On Sat, Jan 31, 2009 at 09:14, Rune Petersen <[email protected]> wrote: > wget is terrible tool for testing hard disk performance, since it is also > dependent on network performance. > > In other words test hard disk and network performance separately.
Ditto, and make sure you're testing network performance and not your internet connection. Most consumer-grade connections tend to vary speeds wildly depending on congestion. In other words, make sure you're testing across a known-speed link, like a 100Mb LAN connection to a PC. > A simple test of hard disk performance: > dd if=/dev/zeero of=/path/to/mount/testfile.bin count=102400 A decent test of write speed (less the 'zeero' typo), the goal is to write more than will be cached in-memory, so a more appropriate size suffix would be "bs=1024 count=X" where X is the size of your memory in KB plus a little (say 50%), so '768000' for 512MB. You also need to test read speed, so change the if/of clause to "if=/dev/your_drive of=/dev/null" to do that. > or hdparm -t /dev/sda A better test of peak sequential read speeds, but '-tT' is better, as it adds cache-speed testing and uses the results from that to temper the actual read test. RB _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
