Article View: borland.public.jbuilder.java.language
Article #15948Re: BufferdInputStream, how they work?
From: Jason C. Leach
Date: Mon, 19 Apr 1999 00:00
Date: Mon, 19 Apr 1999 00:00
15 lines
1295 bytes
1295 bytes
I think it is a block read. Have a look at the little intro paragraph
to the BufferdInputStream in the Help. It is a skimpy description, but
does say by block.
By character may work OK for the JVM. If you do a byte by byte read
from an Exe in say C++ it is really no faster than a block read. This is
due to the HD cache that does a block read. Since the JVM is at a base
level just like any other app, it can probably read byte by byte if need
be and still do alright.
It preformance boos in Java is unreal. I'd say near 100% faster for me.
But, it does not seem to get faster if I increase the size of the
buffer. Anyone know why?
Jason
Technical Details
Message-ID:
<371B7238.F02C01C7@hotmail.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<37166AE3.8D3FA85C@hotmail.com> <3716AAE6.5DCAC629@hotmail.com> <371AEB79.34D6@cwcom.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,5398bd6854fe923e X-Google-Attributes: gidf74b3,public From: "Jason C. Leach" <leachjc@hotmail.com> Subject: Re: BufferdInputStream, how they work? Date: 1999/04/19 Message-ID: <371B7238.F02C01C7@hotmail.com> X-Deja-AN: 468390536 Content-Transfer-Encoding: 7bit References: <37166AE3.8D3FA85C@hotmail.com> <3716AAE6.5DCAC629@hotmail.com> <371AEB79.34D6@cwcom.co.uk> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.jbuilder.java.language