NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Post your performance results
I thought it might be interesting to see what kind of performance everyone is getting with IO Meter so that we can compare what we're getting. So I thought we could all post our results in this thread...
Expanded from my previous post here: /forum/viewtopic.php?t=15033
NAS: NV+, 1GB RAM, 3x500GB disk, X-RAID, Jumbo frames enabled
Network: Netgear GigE switch, w/ Jumbo frame support
Client: AMD X2 4200+ (dual core), running Fedora Core 6 (2.6.22.2-61.fc6), intel GigE nic, mtu=7936
exportopts: insecure,insecure_locks,rw,no_root_squash,async
mountopts: proto=tcp,rsize=8192,wsize=8192,intr,bg
From my linux box:
(write test - default 1k block size)
$ dd if=/dev/zero of=/path/to/file/on/nas count=200000
200000+0 records in
200000+0 records out
102400000 bytes (102MB) copied, 15.2132 seconds, 6.7 MB/s
testing with different block sizes (4k, 8k, 16k, 256k) yields a bit of difference - up to about 8MB/s with 4k blocks.
(read test - default 1k block size)
$ dd if=/path/to/file/on/nas of=/dev/null
200000+0 records in
200000+0 records out
102400000 bytes (102MB) copied, 7.81847 seconds, 13.1 MB/s
playing with different block sizes (bs=#) here (4k, 16k) is tricky - if you re-read the same file, it's cached and you can see upwards of 500MB/sec. If I re-create the file each time, I've seen 15MB/s best case read perf using 4k blocks.
If I ssh onto the device and perform the same tests against the local file system, I get only marginal improvement on write speed - 6.8MB/s write.
Again, results differ with block sizes - best I've found is 18MB/s write w/ 4k blocks.
Read against the local file system is significantly improved, at 31.8MB/s, or 104MB/s with 4k blocks.
When I've got a bit of time, I'm going to see about getting IOMeter working with the manager running on a windows box and dynamo (the test process) on my linux box.
NAS: NV+, 1GB RAM, 3x500GB disk, X-RAID, Jumbo frames enabled
Network: Netgear GigE switch, w/ Jumbo frame support
Client: AMD X2 4200+ (dual core), running Fedora Core 6 (2.6.22.2-61.fc6), intel GigE nic, mtu=7936
exportopts: insecure,insecure_locks,rw,no_root_squash,async
mountopts: proto=tcp,rsize=8192,wsize=8192,intr,bg
From my linux box:
(write test - default 1k block size)
$ dd if=/dev/zero of=/path/to/file/on/nas count=200000
200000+0 records in
200000+0 records out
102400000 bytes (102MB) copied, 15.2132 seconds, 6.7 MB/s
testing with different block sizes (4k, 8k, 16k, 256k) yields a bit of difference - up to about 8MB/s with 4k blocks.
(read test - default 1k block size)
$ dd if=/path/to/file/on/nas of=/dev/null
200000+0 records in
200000+0 records out
102400000 bytes (102MB) copied, 7.81847 seconds, 13.1 MB/s
playing with different block sizes (bs=#) here (4k, 16k) is tricky - if you re-read the same file, it's cached and you can see upwards of 500MB/sec. If I re-create the file each time, I've seen 15MB/s best case read perf using 4k blocks.
If I ssh onto the device and perform the same tests against the local file system, I get only marginal improvement on write speed - 6.8MB/s write.
Again, results differ with block sizes - best I've found is 18MB/s write w/ 4k blocks.
Read against the local file system is significantly improved, at 31.8MB/s, or 104MB/s with 4k blocks.
When I've got a bit of time, I'm going to see about getting IOMeter working with the manager running on a windows box and dynamo (the test process) on my linux box.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
