>>> On Thu, 15 Sep 2005 08:38:16 -0500, Dave Kleikamp >>> <[EMAIL PROTECTED]> said:
[ ... ] >> * Making a file system with a 30MiB log instead of the default >> 32MiB makes reading it with 'tar' over twice as slow. This >> for the same partition on the same hard disc with the same >> content freshly loaded (it was so strange I checked several >> times). shaggy> You're right that this is strange. If you are running shaggy> with noatime, the journal shouldn't be a factor at all shaggy> when reading the volume. This one really puzzles me. I wasn't running with 'noatime', but not to worry. I think it was due to some ATA chipset driver issue, because I have tried to reproduce it later and it did not happen again. However from various tests it looks that when reloading a filesystem from fresh the size of the log seems to have a _small_ (e.g. 10%) influence on how ''fast'' rereading the contents back is. If the log is longer perhaps allocations are more contiguous or whatever... [ ... ] ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
