• Your gigabit network, what kind of speed should you really expect, Part 1 of the Network Performance series

    Network Speed gauge


    Over the weekend I reorganized the HomeNetworkEnabled forums. It had been six months since inception and I had a little time to analyze what was useful and what wasn't. On the useful front, I realized benchmarks of network performance are useful. With this revelation I added two forums to the LAN Speed Test forum, one for wireless speed test results, and another for wired speed test results. As I started to delve in to it a little more however, I realized some context is definitely in order. In what I can only describe as a geeky epiphany, I ran around the house collecting performance figures on all of our devices. I decided to put this together as a 3-part series. The first will explore wired speeds, the second will explore wireless speeds, and the third will look at the effect of antivirus on performance numbers.

    To measure speed around the house I needed a consistent testing protocol. I loaded LST Server (available for $5) on to our repurposed TiVo. The repurposed TiVo is a robust system running an 17-2600k at 3.40GHz, a Realtek PCIe GBE nic, and Windows 7 64-bit. For the clients I used LAN Speed Test v.2.0.8 (100 packets, 1MB test packet size), which is also available as a multiple computer license for $5. It should be noted that LST Server is not necessary, the free LAN Speed Test can speed test to any SMB share. However, with LST Server, the speed tests are done directly to memory vs a share, making performance numbers more accurate. In the case of SMB clients I did have to run LAN Speed Test against their shares. Their performance numbers will be reported separately to compare apples to apples. In all cases virus scan was shut off. On higher end systems I found virus scan made little to no difference in performance numbers. On the mediocre to low-end systems I found the performance dropoff a little alarming, this will be covered in Part 3 of the series.

    So with that, let's look at our chart of performance numbers around the house for Windows machines that I could use LST Server with.

    System CPU CPU Passmark Score (higher is better) OS Network card Wired speed Writing (Mbps) Wired Speed Reading (Mbps)
    Dell Latitude D630 Core2 Duo T7100 1.8GHz 985 Windows XP 32-bit Broadcom NetExtreme
    57xx Gigiabit
    504 394
    Dell Latitude D610 Intel Pentium M 1.86GHz 476 Windows XP 32-bit Broadcom NetExtreme
    57xx Gigiabit
    569 459
    Low power homebrew server Atom D525 1.8GHz dual core 714 Windows Server 2003 32-bit Realtek PCIe GBE 711 400
    Gateway Profile5 desktop Pentium 4 2.6GHz 306 Windows 7 32-bit Intel Pro/1000CT 750 288
    HP 6240f desktop Core2 Quad Q8300 2.5GHz 3555 Windows 7 64-bit Realtek PCIe GBE 835 898
    Repurposed Tivo i7-2600k 3.4GHz quadcore 9086 Windows 7 64-bit Realtek PCIe GBE LST Server host LST Server host

    I organized the above chart by writing speeds. Organized this way, you can see all Windows 7 machines have faster throughput, followed by Windows 2003 Server, and then by XP. As I was running the tests and not looking at the data as a whole, I thought it was fairly obvious to me that faster performance numbers were following the faster systems in a very direct relationship. As I look at the data now, it's definitely not the case. Performance tests between my two high-end systems were exceptional, pulling in almost 90% of the theoretical gigabit limit. The other systems followed a loose pattern with OS being the biggest factor. It would have been interesting to test different OS's on the same hardware to see what numbers came up.

    On reading speeds the order changes in to a pattern with no real explanation. What was surprising to me was the Latitude D630 being bested by the much less of a system Latitude D610. In reading speeds the D610 is #2 out of all the systems.

    System CPU CPU Passmark Score (higher is better) OS Network card Wired speed Writing (Mbps) Wired Speed Reading (Mbps)
    Gateway Profile5 desktop Pentium 4 2.6GHz 306 Windows 7 32-bit Intel Pro/1000CT 750 288
    Dell Latitude D630 Core2 Duo T7100 1.8GHz 985 Windows XP 32-bit Broadcom NetExtreme
    57xx Gigiabit
    504 394
    Low power homebrew server Atom D525 1.8GHz dual core 714 Windows Server 2003 32-bit Realtek PCIe GBE 711 400
    Dell Latitude D610 Intel Pentium M 1.86GHz 476 Windows XP 32-bit Broadcom NetExtreme
    57xx Gigiabit
    569 459
    HP 6240f desktop Core2 Quad Q8300 2.5GHz 3555 Windows 7 64-bit Realtek PCIe GBE 835 898
    Repurposed Tivo i7-2600k 3.4GHz quadcore 9086 Windows 7 64-bit Realtek PCIe GBE LST Server host LST Server host

    The odd thing about all of this is CPU shouldn't be the limiting factor with network throughput. Lesser CPUs can still push fast gigabit speeds, but with the results you can definitely see it was at least a consideration if only seeing the ridiculous throughput between the two quadcores. CPU seemed to be less of a consideration for writing than OS type, but in reading I couldn't see a pattern.

    I asked myself what I considered "acceptable". Even the old, slow Gateway Profile5 was still reading at 288Mbps over the network. While that's less than a third of theoretical gigabit speed, it's still fast relatively speaking when compared to wireless or 100BaseT. That machine is only using that sort of bandwidth on a very rare basis anyway.

    Moving on from the Windows machines, I decided to test all of the SMB clients using LAN Speed Test v2 from our repurposed Tivo. The numbers are below.

    System CPU OS Wired speed Writing (Mbps) Wired speed Reading (Mbps)
    Mac G4 10.4 Tiger 364 332
    Synology DS111
    Marvell Kirkwood mv6282 1.6GHz ARM
    Linux 434 448
    Synology DS109
    Marvell Kirkwood mv6281 1.2GHz ARM
    Linux 468 412
    Vortexbox
    AMD Athlon 2600+ 2.08GHz Socket A
    Fedora 16 527 375

    The DS111 does all of the network backups for our network, so it's truly the bottleneck for all of our PCs, if you can really call it that. At 448Mbps, it's plenty fast for overnight backups. The Vortexbox sends media to a 100BaseT Samsung TV, so those numbers are more than acceptable. The DS109 simply monitors a few 100BaseT IP cameras and does secondary DNS work, so throughput is more than enough there as well. All SMB clients had very respectable numbers compared to the Windows boxes. An interesting test with more time would be to run the LAN Speed Test SMB share test against the Windows boxes as well to get an apples to apples test here.

    In summary, the gigabit theoretical limit of 1000Mbps is just that for most systems, theoretical. The two quadcores got about as close as I've ever seen, and Windows 7 seemed to get you closer as well. Even so, the slowest gigabit speeds are still nearly 3 times as fast as 100BaseT or 450Mbps connected wireless (more to come on that in Part 2). Run some of your numbers and get them in to Wired speed results forum. In Part 2 we'll be looking at realistic wireless results.
    Comments 6 Comments
    1. anmatr's Avatar
      anmatr -
      Thanks.
      Is there a Part 2 of the Network Performance series?
    1. Scott DeLeeuw's Avatar
      Scott DeLeeuw -
      There is, I am just slow getting to it... Did you find this one useful? What would you like to see in part 2?
    1. anmatr's Avatar
      anmatr -
      Yes, it was useful as I started to take my network speed more serious and want to get more out of it with the latest buy.

      I could test my new NAS system so it was useful on the SMB client figures. As I only have an aged laptop with 100BaseT I did not bother testing it for speed. Also as I have the free version of Lan Speed Test I cannot do a multiple test scenario, more the ad hoc tests. My setup is:
      - QNAP TS-569 Pro, Intel Atom 2.13GHz Dual-core, 1 GB RAM
      - RAID 6 with 5x3.5'' SATA 6Gb/s, WD WD20EFRX RPM: IntelliPower ;-) (whatever that is).
      - Server: MS XP x64 SP2, CPU X9650 @ 3.0 GHz, 8GB
      - NIC: Marvell Yukon 88E8056 PCI-E Gigabit Ethernet

      - QNAP TS-219+, Marvell 2.0 GHh, 512 MB DRAM
      - RAID 1 with 2x 3.5'' SATA 6Gb/s, WD WD20EFRX RPM: IntelliPower

      The server is a bit aged now but reliable. The QNAP is brand new and I use the TS-219+ as a backup storage.

      The QNAP TS-569 Pro has about 460 Mbps writing and 380 Mbps reading.
      The QNAP TS 219+ has about 400 Mbps writing and 350 Mbps reading.
      Both on a 1MB file as done in your test.
      What I miss is the details on you harddrives as that must slow down on the SMB clients quite significant. So it would be good to compare like for like. Also the RAID used.

      The wireless would be very interesting too. My current laptop has only the g spec but still interesting to see how it compares.

      Thanks anyway for the details so far!
      Anmatr.
    1. Scott DeLeeuw's Avatar
      Scott DeLeeuw -
      Thanks for the feedback Anmatr! I'll get working on part 2 then, with the holidays here I should actually have some time to do it. In the forums there is also a "Share your results" section you might check out. (Forum -> Network Design and Performance -> Home Network Software -> LAN Speed Test -> Results.

      To answer your questions, both NAS' and the Vortexbox are set up with single drives. The Vortexbox has a 7200rpm drive, whereas the Synology NAS' are set up with 5400rpm drives as I figured they would be cooler running and CPU would be the bottleneck.

      I highly recommend LAN Speed Test v3 and LST Server. They are $5 each, so not a huge investment for the information they give you.
    1. ma3245's Avatar
      ma3245 -
      If I wanted to run the results simultaneously say from 5 workstations to my WHS box as the Lan Test Server, will it be able to do it? if not, do you know of any such utility?

      thank you.
    1. Scott DeLeeuw's Avatar
      Scott DeLeeuw -
      Drop over to the LAN Speed Test forum on this site and ask Pete, the developer, the question. He is always happy to answer.
    + Post Comment