NSLU2-Linux
view · edit · print · history

Info.Performance History

Hide minor edits - Show changes to markup

November 10, 2008, at 09:58 PM by adriansi --
Changed line 353 from:
to:
  • WRT54GL, 250Mhz, dd-wrt
November 10, 2008, at 09:58 PM by adriansi --
Changed line 350 from:
  • HD ST3320620A?(Seagate, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4 enclosure,
to:
  • HD ST3320620A(Seagate, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4 enclosure,
Changed lines 354-356 from:
to:
  • WinXP Sp3, AthlonXP 2500+,1GB, HD SATAI - ST3120026AS
November 10, 2008, at 09:57 PM by adriansi --
Changed line 350 from:
  • HD ST3320620A?(Seagate, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4? enclosure,
to:
  • HD ST3320620A?(Seagate, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4 enclosure,
Changed lines 354-356 from:
to:
Changed lines 360-362 from:
dd:16.9MB/s19.2MB/s
samba:5.0MB/s4-5MB/s
to:
dd16.9MB/s19.2MB/s
samba5.0MB/s4-5MB/s
November 10, 2008, at 09:56 PM by adriansi --
Added line 357:
November 10, 2008, at 09:55 PM by adriansi --
Changed lines 357-361 from:
          read          write
 ftp:      5.6MB/s      6.0MB/s 
 dd:      16.9MB/s     19.2MB/s 
 samba:    5.0MB/s      4-5MB/s 
to:
 READWRITE
ftp5.6MB/s6.0MB/s
dd:16.9MB/s19.2MB/s
samba:5.0MB/s4-5MB/s
November 10, 2008, at 09:53 PM by adriansi --
Changed lines 357-361 from:
          read        write
 ftp:     5.6MB/s     6.0MB/s
 dd:      16.9MB/s     19.2MB/s
 samba:   5.0MB/s     4-5MB/s
to:
          read          write
 ftp:      5.6MB/s      6.0MB/s 
 dd:      16.9MB/s     19.2MB/s 
 samba:    5.0MB/s      4-5MB/s 
November 10, 2008, at 09:52 PM by adriansi --
Changed line 359 from:
 dd:      16.9MB/s    19.2MB/s
to:
 dd:      16.9MB/s     19.2MB/s
Deleted lines 361-367:
        READ      WRITE  

ftp - using ftp command line dd - dd bs=1M count=100 if=/dev/zero of=hugefile.dat

    - clear cache
    - dd bs=1M count=100 of=/dev/null if=hugefile.dat

samba - using total commander

November 10, 2008, at 09:51 PM by adriansi --
Changed lines 359-361 from:
 dd  :    16.9MB/s    19.2MB/s 
 samba:   5.0MB/s     4-5MB/s 
to:
 dd:      16.9MB/s    19.2MB/s
 samba:   5.0MB/s     4-5MB/s
Changed line 364 from:

dd - dd bs=1M count=100 if=/dev/zero of=hugefile.dat \\

to:

dd - dd bs=1M count=100 if=/dev/zero of=hugefile.dat

Changed line 366 from:
    - dd bs=1M count=100 of=/dev/null if=hugefile.dat \\
to:
    - dd bs=1M count=100 of=/dev/null if=hugefile.dat
November 10, 2008, at 09:50 PM by adriansi --
Added lines 356-361:
          read        write
 ftp:     5.6MB/s     6.0MB/s
 dd  :    16.9MB/s    19.2MB/s 
 samba:   5.0MB/s     4-5MB/s 
Changed lines 363-367 from:

ftp 5.6MB/s 6.0MB/s using ftp command line
dd 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat
clear cache; dd bs=1M count=100 of=/dev/null if=hugefile.dat
samba 5.0MB/s 4-5MB/s using total commander

to:

ftp - using ftp command line dd - dd bs=1M count=100 if=/dev/zero of=hugefile.dat
- clear cache

    - dd bs=1M count=100 of=/dev/null if=hugefile.dat 
samba - using total commander
November 10, 2008, at 09:47 PM by adriansi --
Changed lines 357-361 from:
  • ftp 5.6MB/s 6.0MB/s using ftp command line
    *dd 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat
    clear cache; dd bs=1M count=100 of=/dev/null if=hugefile.dat
    *samba 5.0MB/s 4-5MB/s using total commander
to:

ftp 5.6MB/s 6.0MB/s using ftp command line
dd 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat
clear cache; dd bs=1M count=100 of=/dev/null if=hugefile.dat
samba 5.0MB/s 4-5MB/s using total commander

November 10, 2008, at 09:47 PM by adriansi --
Changed lines 356-360 from:

|READ|WRITE|

  • ftp|5.6MB/s6.0MB/s|using ftp command line|
  • dd|16.9MB/s|19.2MB/s|dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache dd bs=1M count=100 of=/dev/null if=hugefile.dat|
  • samba|5.0MB/s|4-5MB/s|using total commander|
to:
        READ      WRITE  
  • ftp 5.6MB/s 6.0MB/s using ftp command line
    *dd 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat
    clear cache; dd bs=1M count=100 of=/dev/null if=hugefile.dat
    *samba 5.0MB/s 4-5MB/s using total commander
November 10, 2008, at 09:43 PM by adriansi --
Changed line 350 from:
  • HD ST3320620A?(Seagata, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4? enclosure,
to:
  • HD ST3320620A?(Seagate, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4? enclosure,
Changed lines 356-361 from:
           READ        WRITE
  • ftp 5.6MB/s 6.0MB/s using ftp command line
  • dd 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache
                                 dd bs=1M count=100 of=/dev/null if=hugefile.dat
  • samba 5.0MB/s 4-5MB/s using total commander
to:

|READ|WRITE|

  • ftp|5.6MB/s6.0MB/s|using ftp command line|
  • dd|16.9MB/s|19.2MB/s|dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache dd bs=1M count=100 of=/dev/null if=hugefile.dat|
  • samba|5.0MB/s|4-5MB/s|using total commander|
November 10, 2008, at 09:39 PM by adriansi --
Changed lines 357-361 from:
  • ftp : 5.6MB/s 6.0MB/s using ftp command line
  • dd : 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache
                                  dd bs=1M count=100 of=/dev/null if=hugefile.dat
  • samba: 5.0MB/s 4-5MB/s using total commander
to:
  • ftp 5.6MB/s 6.0MB/s using ftp command line
  • dd 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache
                                 dd bs=1M count=100 of=/dev/null if=hugefile.dat
  • samba 5.0MB/s 4-5MB/s using total commander
November 10, 2008, at 09:37 PM by adriansi --
Changed lines 357-358 from:

ftp : 5.6MB/s 6.04MB/s using ftp command line dd : 16.9 MB/s 19.2 MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache

to:
  • ftp : 5.6MB/s 6.0MB/s using ftp command line
  • dd : 16.9MB/s 19.2MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache
Changed lines 360-361 from:

samba: 5.0MB/s 4-5MB/s using total commander

to:
  • samba: 5.0MB/s 4-5MB/s using total commander
November 10, 2008, at 09:35 PM by adriansi --
Changed lines 357-364 from:

ftp : 5.6MB/s 6.04MB/s -- using ftp command line

dd : 16.9 MB/s 19.2 MB/s -- dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache

                                  -- dd bs=1M count=100 of=/dev/null if=hugefile.dat

samba: 5.0MB/s 4-5MB/s -- using total commander

to:

ftp : 5.6MB/s 6.04MB/s using ftp command line dd : 16.9 MB/s 19.2 MB/s dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache

                                  dd bs=1M count=100 of=/dev/null if=hugefile.dat

samba: 5.0MB/s 4-5MB/s using total commander

November 10, 2008, at 09:34 PM by adriansi --
Added line 358:
Added line 360:
Added line 362:
November 10, 2008, at 09:33 PM by adriansi -- Additional tests on SlugOS/BE
Added lines 346-362:

Additional tests on SlugOS/BE

Environment:

  • NSLU2 266Mhz, 2.6.16, armv5teb - SlugOS/BE
  • HD ST3320620A?(Seagata, SATAII, 7200rpm, 16MB) in a Thermaltake MAX4? enclosure,
    • filesystem type : ext3 (mounted with -o async and echo 1024> /sys/block/${disk_name}/device/max_sectors)
    • samba (3.0.27a) : socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_SNDBUF=65536 SO_RCVBUF=65536
  • WRT54GL?, 250Mhz, dd-wrt
  • WinXP? Sp3, AthlonXP? 2500+,1GB, HD SATA1? - ST3120026AS?
           READ        WRITE

ftp : 5.6MB/s 6.04MB/s -- using ftp command line dd : 16.9 MB/s 19.2 MB/s -- dd bs=1M count=100 if=/dev/zero of=hugefile.dat, clear cache

                                  -- dd bs=1M count=100 of=/dev/null if=hugefile.dat

samba: 5.0MB/s 4-5MB/s -- using total commander

--adriansi

October 25, 2008, at 01:29 PM by kerry -- Additionnal spelling fix
Changed line 30 from:

Additionnal SAMBA measures on Debian

to:

Additional SAMBA measures on Debian

May 29, 2008, at 11:55 AM by Biboobox -- Cosemtic fix
Changed line 34 from:

Then i got the following results :

to:

Then i got the following results, with the Slug 100% dedicated to the test (ie no other consuming processes running):

Changed lines 38-40 from:
 - From a Vista laptoip, with a 100 MB file, flushing all cache between tests:
            - WRITE : 5.0 MBS (!)
            - READ  : 4.7 MBS (!)
to:
 - From a Vista laptop, with a 100 MB file, flushing all cache between tests:
            - WRITE : 5.0 MBS 
            - READ  : 4.7 MBS 
May 29, 2008, at 11:52 AM by Biboobox -- More info with vista as a samba client
Changed lines 39-42 from:
            - WRITE : 2.0 MBS (!)
            - READ  : 2.0 MBS (!)

The results with the vista laptop are quite back, i am still investigating why.

to:
            - WRITE : 5.0 MBS (!)
            - READ  : 4.7 MBS (!)

Note that for the laptop, the result are horrible when using a wireless connection (ie near 2.0 MBS), but it might be due to the bad routing peformance of my xDSL/WLAN gateway.

May 29, 2008, at 07:14 AM by Biboobox -- Add some SAMBA measurments
Added lines 30-42:

Additionnal SAMBA measures on Debian

I just tweak the following stuff on my NSLU2:

 - Use of writeback journal (available in ext3fs) and noatime mount option
 - In smb.conf, use of : socket options = TCP_NODELAY SO_KEEPALIVE IPTOS_LOWDELAY SO_RCVBUF=16384 SO_SNDBUF=16384

Then i got the following results :

 - From a Linux server, with a 100 MB file, flushing all cache between tests:
            - WRITE : 5.2 MBS
            - READ  : 4.3 MBS
 - From a Vista laptoip, with a 100 MB file, flushing all cache between tests:
            - WRITE : 2.0 MBS (!)
            - READ  : 2.0 MBS (!)

The results with the vista laptop are quite back, i am still investigating why.

Added line 345:
January 29, 2008, at 08:47 PM by Reedy Boy -- debian read speed
Changed line 27 from:
  • Maximum read speed:
to:
  • Maximum read speed: ~3.5MB/s (CPU load ~40%)
January 28, 2008, at 10:11 PM by Reedy Boy -- rem read cpu
Changed line 27 from:
  • Maximum read speed: MB/s (CPU load ~50%)
to:
  • Maximum read speed:
January 28, 2008, at 10:11 PM by Reedy Boy -- add to debian notes
Added lines 25-26:

Tests on a de-underclocked NSLU2 running Debian Etch, kernel 2.6.18.dfsg.1-17. Samba ver: 3.0.24-6etch9

January 28, 2008, at 09:55 PM by Reedy Boy -- samba on debian info - need to add read speed
Added lines 24-27:

Samba on Debian

  • Maximum read speed: MB/s (CPU load ~50%)
  • Maximum write speed: ~4 MB/s (CPU load ~60%)
January 11, 2008, at 01:10 PM by Kassidy Clark --
Changed lines 3-4 from:

A professional report on web server performance from a researcher at the Free University in Amsterdam (http://www.vu.nl) can be found here.

to:

A professional report on web server performance from a researcher at the Free University in Amsterdam can be found here.

January 11, 2008, at 01:07 PM by Kassidy Clark --
Changed lines 3-4 from:

A professional report on web server performance from a researcher at the Free University in Amsterdam can be found here.

to:

A professional report on web server performance from a researcher at the Free University in Amsterdam (http://www.vu.nl) can be found here.

January 11, 2008, at 08:25 AM by Kassidy Clark -- giving credit to the university
Changed lines 3-4 from:

A professional report on web server performance can be found here.

to:

A professional report on web server performance from a researcher at the Free University in Amsterdam can be found here.

January 08, 2008, at 09:18 AM by rwhitby --
Changed lines 3-4 from:

A professional report on web server performance can be found at here.

to:

A professional report on web server performance can be found here.

January 08, 2008, at 09:18 AM by rwhitby --
Changed lines 3-4 from:

A professional report on web server performance can be found at Attach:SLUG_performance_report.pdf here Δ.

to:

A professional report on web server performance can be found at here.

January 08, 2008, at 09:17 AM by rwhitby -- Added the slug performance report
Changed lines 3-4 from:

A professional report on web server performance can be found at [Attach:SLUG_performance_report.pdf here].

to:

A professional report on web server performance can be found at Attach:SLUG_performance_report.pdf here Δ.

January 08, 2008, at 09:17 AM by rwhitby --
Changed lines 3-4 from:

A professional report on web server performance can be found at Attach:SLUG_performance_report.pdf

to:

A professional report on web server performance can be found at [Attach:SLUG_performance_report.pdf here].

January 08, 2008, at 09:17 AM by rwhitby --
Changed lines 3-4 from:

A professional report on web server performance can be found at attach:SLUG_performance_report.pdf

to:

A professional report on web server performance can be found at Attach:SLUG_performance_report.pdf

January 08, 2008, at 09:15 AM by rwhitby --
Added lines 3-4:

A professional report on web server performance can be found at attach:SLUG_performance_report.pdf

August 06, 2007, at 10:08 PM by marceln -- removed false wikilinks
Changed line 78 from:
 I also have that 16 port hub connected to a netgear FM114P router, and when
to:
 I also have that 16 port hub connected to a netgear FM114P router, and when
March 03, 2007, at 01:15 AM by Blastur -- Removed dead link to http://paranoidpenguin.blogspot.com/2006/02/secure-file-serving-part-2.html
Deleted lines 51-54:

More Benchmarks

A good set of throughput test results for an overclocked NSLU2 (along with enough information to reproduce the tests) are available at http://paranoidpenguin.blogspot.com/2006/02/secure-file-serving-part-2.html .

Changed lines 96-99 from:
  • Toshiba MK5026GAX 40GB 5400rpm 2.5 Drive
  • Vantec Nexstar USB2 2.5 case
to:
  • Toshiba MK5026GAX 40GB 5400rpm 2.5” Drive
  • Vantec Nexstar USB2 2.5” case
July 02, 2006, at 08:48 AM by Nate S -- changed Samsung 160BG to Samsung 160GB for size of hard drive
Changed lines 7-8 from:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - http://www.sweex.nl - using the ALI chip) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your performance numbers differ significantly from mine.

to:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - http://www.sweex.nl - using the ALI chip) with a Samsung 160GB 7.2krpm and 8 MB cache. Please update if your performance numbers differ significantly from mine.

February 14, 2006, at 02:04 AM by quandary -- Added a link to more benchmark results
Added lines 52-55:

More Benchmarks

A good set of throughput test results for an overclocked NSLU2 (along with enough information to reproduce the tests) are available at http://paranoidpenguin.blogspot.com/2006/02/secure-file-serving-part-2.html .

January 14, 2006, at 06:09 PM by Xnaron -- Question
Added lines 15-16:

Question: Does the overclock mod alter the speeds below for Samba?

November 30, 2005, at 10:47 PM by Zhyla -- notes about NFS throughput tuning w/ rsize,wsize
Added lines 26-27:

The rsize and wsize options for NFS have a huge impact, try setting them to 32768 or 65536. I'm getting 4.75/3.5 MB/s (read/write), see my profile - Profiles.Zhyla

March 12, 2005, at 09:18 PM by yahpn --
Added lines 300-319:

Dhrystone

The Dhrystone benchmark mostly runs from cache and says something about CPU performance but relatively little about overall system performance. The system is an unmodfied NSLU2 (except for serial port addition) running Unslung 3.18 beta, gcc 3.3.5 with stock libs and compiler flags "-O3 -mcpu=xscale".

Dhrystone 2.1:

Microseconds for one run through Dhrystone: 6.4 Dhrystones per Second: 155440.4 VAX MIPS rating = 88.469

Dhrystone 1.1:

Dhrystone( 1.1) time for 3000000 passes = 16.4 Register option selected? NO This machine benchmarks at 182815.4 dhrystones/second VAX MIPS rating = 104.050

These results look low to me for a 266 MHz xscale so I checked the rate at which the performance monitor register CCNT counts and saw 133 MHz. Maybe the core on the NSLU2 is running only at 133 MHz. Some other xscales have a frequency change procedure that kernels or bootloaders can get wrong-- but no such procedure appears to be documented for the IXP420. For comparison, my 233 MHz Pentium2 MMX running NetBSD 1.6.2 yields 189 and 213 VAX MIPS from Dhrystone 2.1 and 1.1 respectively.

-- yahpn

March 02, 2005, at 10:19 AM by bobtm --
Changed line 9 from:

I have compared the NSLU2 to similar products. One of the closest, the Synology DS-101, has slightly better performance, probably due to more RAM and use of IDE disks rather than USB. Until it has been "Unsyned", the actual cause of the higher speed is uncertain.

to:

I have compared the NSLU2 to similar products. One of the closest, the Synology DS-101, has slightly better performance, probably due to more RAM and use of IDE disks rather than USB. Until it has been "Unsyned", the actual cause of the higher speed is uncertain. A performance comparation of NSLU2 and DS-101 (and the Kuro-box) using iozone can be found at http://www.tomsnetworking.com/Reviews-190-ProdID-DS101-5.php .

February 08, 2005, at 06:20 PM by bobtm --
Changed line 7 from:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - www.sweex.nl - using the ALI chip) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your performance numbers differ significantly from mine.

to:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - http://www.sweex.nl - using the ALI chip) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your performance numbers differ significantly from mine.

Changed line 35 from:

Write speed measured using "time dd bs=1M count=100 if=/dev/zero of=hugefile.dat" on /share/hdd/data/public and readspeed with "time dd bs=1M count=100 of=/dev/null if=hugefile.dat" (remember to empty any cache between write and read test). Also note that "time" is a part of the package Busybox 1.0. You may use your stopwatch if you are reluctant to install it.

to:

Write speed measured using time dd bs=1M count=100 if=/dev/zero of=hugefile.dat on /share/hdd/data/public and readspeed with time dd bs=1M count=100 of=/dev/null if=hugefile.dat (remember to empty any cache between write and read test). Also note that time is a part of the package Busybox 1.0. You may use your stopwatch if you are reluctant to install it.

Changed line 52 from:
  • Run disk benchmarks directly on the slug (dd is a good thing)
to:
  • Run disk benchmarks directly on the slug (dd is a good thing)
January 18, 2005, at 11:11 PM by Jason O039Rourke --
Added line 72:
 [DAVID- 100/half duplex is still a problem.  LED doesn't indicate half/full.]
January 17, 2005, at 09:36 AM by bobtm --
Changed line 5 from:

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN performing large sequential read or writes the NLSU2? will utilize it fully, so this is only relelvant for 100Mb and faster networks. Note that Unslung firmware does not seem to alter the network performance significantly.

to:

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN performing large sequential read or writes the NLSU2 will utilize it fully, so this is only relelvant for 100Mb and faster networks. Note that Unslung firmware does not seem to alter the network performance significantly.

Changed line 13 from:

We should probably test using standard storage benchmark programs too - a couple that spring to mind are IOMeter? and Bonnie (would prefer Spec SFS 3 but complex and not free to set up).

to:

We should probably test using standard storage benchmark programs too - a couple that spring to mind are IOMeter and Bonnie (would prefer Spec SFS 3 but complex and not free to set up).

Added lines 24-25:

For speed measurement for one of the NFS packages, see http://www.nslu2-linux.org/wiki/Unslung/Nfs-utils Unslung.Nfs-utils.

Added lines 48-83:

Troubleshooting

There are a number of possible causes for bad performance. Here are some things to look at:

  • Run disk benchmarks directly on the slug (dd is a good thing)
  • Check the switch/hub LEDs that your slug is detected as a 100Mb/s device.
  • Run ifconfig and look for collisions, dropped packets, overruns and things like that
  • Run netio to see if there is anything in the network path that obstructs. A common problem is bad cables.
  • Check out the duplex issue if possible (see below)

table border=0 width=100% bgcolor=#eeffee? cell?

 > I got into this discussion over on DSL Reports. The leading theory
 > is a problem in the switch/hub detecting full or half duplex. One of
 > the posters had a nice switch and was able to catch the errors from
 > the NSLU. I had the problem with my CNet switch, it liked my Linksys
 > switch and it likes my Nortel switch. I was going to play with my
 > Nortel switch to verify his info, but I have not had the time. I
 > would blame your switch for now.

 I guess that IS possible (I thought about it), but the netgear hub I have
 here does have a 10mb led, and a 100mb led, and when the device is plugged
 in, the 100mb led is lit (this is the Netgear 16-port hub).

 I also have that 16 port hub connected to a netgear FM114P router, and when
 I connect it to that...it works at full-speed again! Dang, definitely
 something with the drivers/chipset negotiating line speed.

 Sounds like something needs to be tweaked in the NSLU2's lan negotiation.

 David Troesch | Atlanta, GA | ICQ# 2333123

tableend?

Added line 298:

January 13, 2005, at 07:59 AM by uSURPER --
Changed line 5 from:

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN, NLSU2? will utilize it fully, so this is only relelvant for 100Mb and faster networks. Note that Unslung firmware does not seem to alter the network performance significantly.

to:

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN performing large sequential read or writes the NLSU2? will utilize it fully, so this is only relelvant for 100Mb and faster networks. Note that Unslung firmware does not seem to alter the network performance significantly.

January 13, 2005, at 07:57 AM by uSURPER --
Changed line 5 from:

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN, NLSU2? will utilize it fully, so this is only relelvant for 100Mb and 100/1000Mb networks. Note that Unslung firmware does not seem to alter the network performance significantly.

to:

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN, NLSU2? will utilize it fully, so this is only relelvant for 100Mb and faster networks. Note that Unslung firmware does not seem to alter the network performance significantly.

Added lines 12-13:

We should probably test using standard storage benchmark programs too - a couple that spring to mind are IOMeter? and Bonnie (would prefer Spec SFS 3 but complex and not free to set up).

January 12, 2005, at 11:48 PM by bobtm --
Changed line 3 from:

What to expect

to:

Overview: What to expect

Changed line 31 from:

Write speed measured using "time dd bs=1M count=100 if=/dev/zero of=hugefile.dat" on /share/hdd/data/public and readspeed with "time dd bs=1M count=100 of=/dev/null if=hugefile.dat" (remember to empty any cache between write and read test).

to:

Write speed measured using "time dd bs=1M count=100 if=/dev/zero of=hugefile.dat" on /share/hdd/data/public and readspeed with "time dd bs=1M count=100 of=/dev/null if=hugefile.dat" (remember to empty any cache between write and read test). Also note that "time" is a part of the package Busybox 1.0. You may use your stopwatch if you are reluctant to install it.

Added lines 43-256:

Details - hard numbers

Lmbench results for Stock Slug with 2.4.22-Linksys kernel.

Hardware:

  • Stock NLSU2,
  • Toshiba MK5026GAX 40GB 5400rpm 2.5 Drive
  • Vantec Nexstar USB2 2.5 case

with CSR loaded:


 Results going to ../results/armv5b-linux-gnu/LKG0FB07F?.
 Using config in CONFIG.LKG0FB07F
 Tue Sep 21 00:34:20 MDT 2004
 Latency measurements
 Tue Sep 21 00:39:56 MDT 2004
 Calculating file system latency
 Tue Sep 21 00:40:18 MDT 2004
 Local networking
 Tue Sep 21 00:40:54 MDT 2004
 Bandwidth measurements
 Tue Sep 21 01:53:08 MDT 2004
 Calculating context switch overhead
 Tue Sep 21 02:07:41 MDT 2004
 Calculating memory load latency
 Tue Sep 21 02:13:30 MDT 2004
 make[1]: Leaving directory `/home/packages/lmbench/lmbench-2.0.4/src'

 real    102m23.363s
 user    80m48.670s
 sys     20m6.560s

without CSR loaded:


 Results going to ../results/armv5b-linux-gnu/LKG000000?.0
 Using config in CONFIG.LKG000000?
 Tue Sep 21 02:32:23 MDT 2004
 Latency measurements
 Tue Sep 21 02:33:04 MDT 2004
 Calculating file system latency
 Tue Sep 21 02:33:27 MDT 2004
 Local networking
 Tue Sep 21 02:33:54 MDT 2004
 Bandwidth measurements
 Tue Sep 21 02:41:49 MDT 2004
 Calculating context switch overhead
 Tue Sep 21 02:43:41 MDT 2004
 Calculating memory load latency
 Tue Sep 21 02:49:05 MDT 2004
 make[1]: Leaving directory `/home/packages/lmbench/lmbench-2.0.4/src'

 real    17m46.969s 
 user    14m12.840s
 sys     2m48.130s

with CSR loaded:


 sh-2.05b# ./hdparm -Tt /dev/sda

 /dev/sda: 
  Timing cached reads:   148 MB in  2.00 seconds =  74.00 MB/sec
  Timing buffered disk reads:   20 MB in  3.03 seconds =   6.60 MB/sec

 /dev/sda:
  Timing cached reads:   148 MB in  2.02 seconds =  73.27 MB/sec
  Timing buffered disk reads:   24 MB in  3.21 seconds =   7.48 MB/sec

 /dev/sda:
  Timing cached reads:   148 MB in  2.00 seconds =  74.00 MB/sec
  Timing buffered disk reads:   24 MB in  3.06 seconds =   7.84 MB/sec

 /dev/sda:
  Timing cached reads:   148 MB in  2.02 seconds =  73.27 MB/sec
  Timing buffered disk reads:   24 MB in  3.09 seconds =   7.77 MB/sec

 /dev/sda:
  Timing cached reads:   148 MB in  2.01 seconds =  73.63 MB/sec
  Timing buffered disk reads:   24 MB in  3.07 seconds =   7.82 MB/sec

without CSR loaded:


 sh-2.05b# ./hdparm -Tt /dev/sda

 /dev/sda:
  Timing cached reads:   164 MB in  2.01 seconds =  81.59 MB/sec
  Timing buffered disk reads:   22 MB in  3.02 seconds =   7.28 MB/sec

 /dev/sda:
  Timing cached reads:   164 MB in  2.02 seconds =  81.19 MB/sec
  Timing buffered disk reads:   24 MB in  3.17 seconds =   7.57 MB/sec

 /dev/sda:
  Timing cached reads:   164 MB in  2.02 seconds =  81.19 MB/sec
  Timing buffered disk reads:   24 MB in  3.07 seconds =   7.82 MB/sec

 /dev/sda:
  Timing cached reads:   164 MB in  2.02 seconds =  81.19 MB/sec
  Timing buffered disk reads:   26 MB in  3.17 seconds =   8.20 MB/sec

 /dev/sda:
  Timing cached reads:   164 MB in  2.02 seconds =  81.19 MB/sec
  Timing buffered disk reads:   26 MB in  3.16 seconds =   8.23 MB/sec

without CSR loaded:


 make on perl-5.8.3:
 real    80m43.326s
 user    76m39.070s
 sys     3m12.650s

with CSR loaded:


 make on perl-5.8.3:
 real    90m48.799s
 user    81m40.610s
 sys     8m1.640s 


                 L M B E N C H  2 . 0   S U M M A R Y
                 ------------------------------------


 Basic system parameters
 ----------------------------------------------------
 Host                 OS Description              Mhz

 --------- ------------- ----------------------- ----
 LKG000000 Linux 2.4.22-        armv5b-linux-gnu  266
 LKG0FB07F Linux 2.4.22-        armv5b-linux-gnu  266
 familiar  Linux 2.4.19-      armv5tel-linux-gnu  400

 Processor, Processes - times in microseconds - smaller is better
 ----------------------------------------------------------------
 Host                 OS  Mhz null null      open selct sig  sig  fork exec sh  
                              call  I/O stat clos TCP   inst hndl proc proc proc
 --------- ------------- ---- ---- ---- ---- ---- ----- ---- ---- ---- ---- ----
 LKG000000 Linux 2.4.22-  266 1.23 3.10 17.5 23.6 211.6 9.19 14.0 3200 11.K 41.K
 LKG0FB07F Linux 2.4.22-  266 1.28 3.23 18.3 24.7 221.5 9.58 14.6 3500 12.K 44.K
 familiar  Linux 2.4.19-  400 0.37 1.03 59.9 61.6  70.4 2.85 4.62 1864 5434 15.K

 Context switching - times in microseconds - smaller is better
 -------------------------------------------------------------
 Host                 OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
                         ctxsw  ctxsw  ctxsw ctxsw  ctxsw   ctxsw   ctxsw
 --------- ------------- ----- ------ ------ ------ ------ ------- -------
 LKG000000 Linux 2.4.22- 151.2  300.4  695.6  338.8  708.8   339.0   733.6
 LKG0FB07F Linux 2.4.22- 178.7  343.5  770.3  378.6  783.2   385.0   784.2
 familiar  Linux 2.4.19- 109.0  293.3  800.5  294.5  824.6   308.0   823.9

 *Local* Communication latencies in microseconds - smaller is better
 -------------------------------------------------------------------
 Host                 OS 2p/0K  Pipe AF     UDP  RPC/   TCP  RPC/ TCP
                         ctxsw       UNIX         UDP         TCP conn
 --------- ------------- ----- ----- ---- ----- ----- ----- ----- ----
 LKG000000 Linux 2.4.22- 151.2 322.4 482.             755.4       1415
 LKG0FB07F Linux 2.4.22- 178.7 375.1 967.             855.0           
 familiar  Linux 2.4.19- 109.0 217.3 342. 544.7 729.0 684.4 1011. 1567

 File & VM system latencies in microseconds - smaller is better
 --------------------------------------------------------------
 Host                 OS   0K File      10K File      Mmap    Prot    Page	
                         Create Delete Create Delete  Latency Fault   Fault 
 --------- ------------- ------ ------ ------ ------  ------- -----   ----- 
 LKG000000 Linux 2.4.22-  747.4  188.6 1851.9  444.6   1734.0 5.026    30.0
 LKG0FB07F Linux 2.4.22-  789.9  205.6 1972.4  793.7   1866.0 5.211    31.0
 familiar  Linux 2.4.19-   14.4   11.5   97.0   21.9   2141.0 2.060    13.0

 *Local* Communication bandwidths in MB/s - bigger is better
 -----------------------------------------------------------
 Host                OS  Pipe AF    TCP  File   Mmap  Bcopy  Bcopy  Mem   Mem
                              UNIX      reread reread (libc) (hand) read write
 --------- ------------- ---- ---- ---- ------ ------ ------ ------ ---- -----
 LKG000000 Linux 2.4.22- 9.02 18.8 16.1   25.6   64.3   43.6   43.3 64.3  84.6
 LKG0FB07F Linux 2.4.22- 7.71 17.1 15.0   24.3   60.4   39.2   38.9 60.5  78.2
 familiar  Linux 2.4.19- 18.0 38.4 21.8   43.5   79.6  118.7   49.8 78.8 334.6

 Memory latencies in nanoseconds - smaller is better
     (WARNING - may not be correct, check graphs)
 ---------------------------------------------------
 Host                 OS   Mhz  L1 $   L2 $    Main mem    Guesses
 --------- -------------  ---- ----- ------    --------    -------
 LKG000000 Linux 2.4.22-   266  16.1  236.3  246.2    No L2 cache?
 LKG0FB07F Linux 2.4.22-   266  17.0  266.2  266.2    No L2 cache?
 familiar  Linux 2.4.19-   400 7.540  302.7  322.5    No L2 cache?

--jacques


Some tests done with the copy of a 200MB file between a NSLU2 with 2.12-beta firmware and a Linux 2.8 (ubuntu), the test was performed with the filesystem "mounted" and then a simple read/write of the 200MB via a python script.

          read        write
 nfs:     5.7MB/s     2.6MB/s 
 cifs:    3.5MB/s     1.9MB/s 
 samba:   2.2MB/s     1.85MB/s 

 nfs-server Version: 2.2beta47-2

--titoo

January 12, 2005, at 10:00 PM by bobtm --
Changed line 31 from:

Measured using C programs using unbuffered reads and writes.

to:

Write speed measured using "time dd bs=1M count=100 if=/dev/zero of=hugefile.dat" on /share/hdd/data/public and readspeed with "time dd bs=1M count=100 of=/dev/null if=hugefile.dat" (remember to empty any cache between write and read test).

Changed line 34 from:
  • Maximum write speed: ~6.5 MB/s (CPU load ~75%)
to:
  • Maximum write speed: ~7.3 MB/s (CPU load ~75%)
January 11, 2005, at 01:41 PM by bobtm --
Changed line 7 from:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - www.sweex.nl - using the ALI chip) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your number differ significantly from mine.

to:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - www.sweex.nl - using the ALI chip) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your performance numbers differ significantly from mine.

January 11, 2005, at 01:40 PM by bobtm --
Added lines 11-12:

Samba and FTP tests are done with single client only. Superficial testing with two clients indicates slightly higher joint throughput. Pure disk and network tests should not differ significantly when having several instances of the test program.

January 11, 2005, at 01:09 PM by bobtm --
Added lines 22-23:

Measured with vsftpd.

Added lines 29-30:

Measured using C programs using unbuffered reads and writes.

Added lines 35-37:

Measured using netio (slug binary version downloadable from http://folk.uio.no/ingeba/netio.arm and x86 linux version http://folk.uio.no/ingeba/netio.x86 . Source can be fetched from http://www.netfuse.de/techarea/netio/netio114.zip ).

January 11, 2005, at 01:04 PM by bobtm --
Changed line 7 from:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - www.sweex.nl) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your number differ significantly from mine.

to:

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - www.sweex.nl - using the ALI chip) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your number differ significantly from mine.

January 11, 2005, at 01:04 PM by bobtm --
Changed lines 1-34 from:

Describe {{Performance}} here.

to:

NSLU2 performance

What to expect

It will of course depend on your LAN, disk and USB enclosure. On a 10Mb LAN, NLSU2? will utilize it fully, so this is only relelvant for 100Mb and 100/1000Mb networks. Note that Unslung firmware does not seem to alter the network performance significantly.

The results below are obtained with Unslung 3.17 using a USB 2.0 enclosure (Sweex - www.sweex.nl) with a Samsung 160BG 7.2krpm and 8 MB cache. Please update if your number differ significantly from mine.

I have compared the NSLU2 to similar products. One of the closest, the Synology DS-101, has slightly better performance, probably due to more RAM and use of IDE disks rather than USB. Until it has been "Unsyned", the actual cause of the higher speed is uncertain.

Samba

  • Maximum read speed: ~3.5 MB/s (CPU load ~50%)
  • Maximum write speed: ~3 MB/s (CPU load ~60%)

NFS

I don't use NFS, but posts from others seem to indicate about the same, or slightly higher, speeds as with Samba, but with more CPU load.

FTP

  • Maximum read speed: ~5.8 MB/s (CPU load ~65%)
  • Maximum write speed: ~4.7 MB/s (CPU load ~70%)

Disk speed

  • Maximum read speed: ~8.7 MB/s (CPU load ~60%)
  • Maximum write speed: ~6.5 MB/s (CPU load ~75%)

Network speed

  • Maximum read speed: ~11.5 MB/s (CPU load ~80%)
  • Maximum write speed: ~11 MB/s (CPU load ~85%)
Page last modified on November 10, 2008, at 09:58 PM