CAT-6 Cable: What Speeds Should I Be Expecting?

23,278

Solution 1

Alright, found my problem, so unfortunately I'm going to have to mark my own answer as correct - I'm upvoting everyone who's answered me here as there is some great stuff in your posts.

The problem for me was that my NIC card in my laptop is a "Broadcom NetXtreme Gigabit" card. I'm not entirely sure what the problem is, but if I use my laptop against my Linux server, the results are quite different:

eddie@prowl ~ $ iperf -c 10.0.0.10 2>&1
------------------------------------------------------------
Client connecting to 10.0.0.10, TCP port 5001
TCP window size:   129 KByte (default)
------------------------------------------------------------
[  3] local 10.0.0.216 port 52201 connected with 10.0.0.10 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  1.07 GBytes    920 Mbits/sec

I'm guessing the issue has something to do with the following [source]:

Why is there no option to force the speed and duplex to 1000Mb/s - Full Duplex?

Per the IEEE standard, the only IEEE compliant way to operate at 1000Mb/s-Full duplex is through auto-negotiation. If the network switch being used is IEEE compliant, the link speed will auto-negotiate to 1000Mb/s-Full duplex when autoneg is selected.

All in all I'm happy. One day I'll figure out the PC laptop's issue, but for now, if I can achieve 920 Mbit/sec with iperf, at least that means I'm capable of higher speeds than 480!

Thanks for all the help all. Hope this helps someone else out there.

Solution 2

I'd say that your results look good. There are many other things which impact network speeds. Both the Mac and the PC may have Gigabit network cards, but not all network cards are same.

In general on older PCs Gigabit network cards use PCI slots which are bottlenecks. This is especially true for integrated cards. Also integrated cards usually have cheap chipsets which offload some of the work to the CPU. This negatively impacts network performance.

Another thing that comes to mind is MTU size. It can impact network speeds. Try enabling Jumbo Frames if they are disabled and see what happens.

Also, just as a sidenote, I never managed to get more than 350Mb/s using a patch cable connecting my laptop and desktop (I can't remember network cards at the moment, sorry).

Solution 3

My Setup

MacBook <---> TimeCapsule <---> PC

Both the MacBook and my PC have a GBit ethernet NIC and the TimeCapsule has a GBit ethernet Switch.

lennart@carla:~$ iperf -s 
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.5 port 5001 connected with 192.168.1.10 port 61313
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec  1.02 GBytes    875 Mbits/sec
[  5] local 192.168.1.5 port 5001 connected with 192.168.1.10 port 61317
[  5]  0.0-30.0 sec  3.07 GBytes    879 Mbits/sec

That's about 100 MByte/sec. I remember having speeds around 60MByte/s when transferring files from one PC to another, but i think the bottleneck was the harddrive in this case.

Note: Setting the window size to 256 KB manually with -w 256 slowed everything down. I don't know how the default window size is determined.

[edit] I'm usin cat5e cables here. Longest link: about 10 meters.

Solution 4

Getting GigE speed between two devices takes doing. There are many non-cabling factors that can affect throughput. First and foremost, TCP/IP itself may cause throttling depending on how the IP stacks of both devices interoperate. Get it really wrong and you can be limited to a swanky 15Kb/s. Also how either stack handles even simple failures can have a big impact on perceived bandwidth usage if the test is short enough for the errors frequent enough. And then there are device-level bottlenecks. Not all GigE cards are capable of shoveling packets that fast even under ideal conditions.

Solution 5

I haven't had much experience testing CAT cables, but for most other things a system is only as good as its weakest part. So, even if you have CAT 6 cables capable of high speeds, you will be limited by the speed of whatever other cable you're using.

Cat 5 and Cat 5e UTP cables can support 10/100/1000 Mbps Ethernet. Although Cat 5 cable may support to some degree in Gigabit Ethernet (1000 Mbps), it performs below standard during high-data transfer scenarios, so I do not recommend you to use Cat 5 cable in Gigabit Ethernet, use Cat 5e instead (of course Cat 6 is the best).

Cat 6 UTP cable is manufactured targeting on Gigabit Ethernet and backward compatible with 10/100 Mbps Ethernet. It performs better then Cat 5 cable with higher transmission rate and lower transmission error. If you plan to have Gigabit network, look for Cat 5e or Cat 6 UTP cables.

Source

Share:
23,278

Related videos on Youtube

Eddie Parker
Author by

Eddie Parker

Updated on September 17, 2022

Comments

  • Eddie Parker
    Eddie Parker over 1 year

    I've just ran a CAT-6 cable throughout my house. I've terminated both my ends using a CAT-6 patch panel and a CAT-6 keystone jack.

    I've put two computers on either end (Macbook Pro 13"; I believe capable of a Gbps, and a Gateway PC that is definitely capable of a Gbps), set them up on the same network (manually assigning an address of 192.168.0.1/24 and 192.168.0.2/24), and ran iperf. There is no switch, hub, or any other network device inbetween: just the two laptops, connected via patch cable to either a keystone jack, or a patch panel.

    The results are as follows:

    eddie@prowl ~ $ iperf -s
    ------------------------------------------------------------
    Server listening on TCP port 5001
    TCP window size:   256 KByte (default)
    ------------------------------------------------------------
    [  4] local 192.168.0.2 port 5001 connected with 192.168.0.1 port 1303
    [ ID] Interval       Transfer     Bandwidth
    [  4]  0.0-10.0 sec    560 MBytes    470 Mbits/sec
    [  4] local 192.168.0.2 port 5001 connected with 192.168.0.1 port 1304
    [ ID] Interval       Transfer     Bandwidth
    [  4]  0.0-10.0 sec    559 MBytes    469 Mbits/sec
    

    As I understand it, the theoretical maximum I should get would be about 1000 Mbit, or 1 Gbit. Unless I'm mistaken, what I'm seeing is exactly half of that.

    Now, the known problem I have is that I used patch cable to attach to the patch panel and the keystone jack, and I'm wagering those are CAT-5 or CAT-5e at best.

    Anyhow, my question as it stands is whether I should be happy with the output of this cable as is, or if I should be investing in some CAT-6 patch cable (I plan to anyhow later, but for testing purposes now, I'm curious if I should get some immediately) to improve those numbers.

    Thanks.

    • Joe_Rose
      Joe_Rose over 13 years
      You left out something very important: is there a switch or router? If so, what model/speed?
    • Eddie Parker
      Eddie Parker over 13 years
      Good point. I'll update the question here, but in this test - no. It's just going straight through the patch panel.
  • Eddie Parker
    Eddie Parker over 13 years
    Great comment - thanks. The 350Mb/s - that was using CAT5 or CAT5e, do you know? If CAT5e, that makes me feel better about the ~500 I'm getting.
  • Eddie Parker
    Eddie Parker over 13 years
    Awesome - that at least confirms that my suspicion could be correct (the possibility of the patch cable causing the issue). Even so, it's good to know that ~500 isn't terrible, even if it is rated Gigabit.
  • user3660103
    user3660103 over 13 years
    @Eddie Parker That was 1 meter long CAT5e cable.
  • user3660103
    user3660103 over 13 years
    In telecommunications, full duplex basically means that both sides can transmit data at the same time. Half duplex means that while one side is transmitting, the other side has to wait until first is finished (or a predetermined amount of time passes and first side makes a pause so that second can report if it has something to transmit or not).
  • user3660103
    user3660103 over 13 years
    There shouldn't be a major impact when one side is just transmitting and the other side is just listening, but some impact is possible. Still, the two sides should auto-negotiate settings. If they badly detected each-others capabilities, some hand tuning could help.
  • Brad
    Brad over 13 years
    Eddie, I highly doubt your cable is the problem here. If you have a link at a given rate, then your card runs at that rate. If you want to confirm this, then check the error count.
  • Eddie Parker
    Eddie Parker over 13 years
    You're just showing off. :P Did you have to tweak any of the settings on the MacBook or PC? Frames, MTU, duplexing? I wonder if the GBit switch is helping things 'sense' full duplex or some such.
  • lajuette
    lajuette over 13 years
    Hehe, no, i'm not showing of. I'm using the default settings. FYI: The PC is a Zotac Ion ITX-A. What i'm trying to say: I wouldn't be satisfied with 470 MBit/s! And i forgot to mention: I'm using cat5e cables.
  • Eddie Parker
    Eddie Parker over 13 years
    Was just teasing on the "showing off" comment. :) Much appreciated to get some realistic benchmarks. I'm now rocking ~920 Mbits/sec. Now I just have to wait until 10 Gbit cards are affordable to truly test out the CAT-6... :D
  • user3660103
    user3660103 over 13 years
    Thanks for info about network card! I a card from same series on my laptop too, so that means that there is still hope for my low transfer speeds!
  • lajuette
    lajuette over 13 years
    @AndrejaKo: wow, that's definitely to slow. Have you tried using another cat5e cable? see my benchmarks below.
  • user3660103
    user3660103 over 13 years
    @lajuette As I said in another comment, I was using short piece of Cat5e cable. Anyway, since I saw high benchmarks, I'm going to start experimenting with new drivers and Cat6 cable.
  • lajuette
    lajuette over 13 years
    i meant that you should replace your short cat5e cable with another cat5e cable. I was using cat5e, too, and got about 870 MBit/s. But trying new drivers might do the trick, too.