Comments on: IO performance – Tar vs. File vs. Byte streams http://chaoticjava.com/posts/io-performance-tar-file-bytes/ The internet, design patterns, frameworks and Java Wed, 08 Sep 2010 10:18:29 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: Aviad http://chaoticjava.com/posts/io-performance-tar-file-bytes/comment-page-1/#comment-44374 Aviad Mon, 08 Dec 2008 21:24:27 +0000 http://chaoticjava.com/?p=240#comment-44374 @Omry: Correct, my mistake. Through our talks on the subject off-blog, I've realised I completely forgot about DataInputStream! @Omry: Correct, my mistake. Through our talks on the subject off-blog, I’ve realised I completely forgot about DataInputStream!

]]> By: Omry http://chaoticjava.com/posts/io-performance-tar-file-bytes/comment-page-1/#comment-44293 Omry Sun, 07 Dec 2008 10:14:52 +0000 http://chaoticjava.com/?p=240#comment-44293 A small mistake: byte[] bytes = new byte[file.length()]; stream.read(bytes); is not guaranties to read enough data to fill up the entire array, quoting the javadoc from FileInputStream: * Reads up to <code>b.length</code> bytes of data from this input * stream into an array of bytes. This method blocks until some input * is available. about tar performance, I am not surprise. the overhead of opening many files can be significant. you will find that the operating system and file system also plays a major role in file IO performance. A small mistake:

byte[] bytes = new byte[file.length()];
stream.read(bytes);

is not guaranties to read enough data to fill up the entire array, quoting the javadoc from FileInputStream:
* Reads up to b.length bytes of data from this input
* stream into an array of bytes. This method blocks until some input
* is available.

about tar performance, I am not surprise.
the overhead of opening many files can be significant.
you will find that the operating system and file system also plays a major role in file IO performance.

]]>