Yes it does support testing of 10Gbit/s NICs. But there are often bottle necks that prevent you getting close to the maximum speed. See FAQ below for details.
One solution to avoid bottle necks is by running multiple instances of the test at the same time. This can be done by launching two copies of PerformanceTest and running the Advanced Netowrk Test on two different IP ports. For example ports 1040 and 1041.
What are expected speeds for a 1Gb network card
On a 1Gb Ethernet link you should get around 900 to 950Mbit/sec, in ideal conditions. There are lots of good reasons why you might not see this level of performance however.
Example LAN bandwidth graph
This was on a 1Gb Ethernet link on a local area network.
What are possible performance bottle necks for network speeds
Here are some of the reasons you might be seeing the bandwidth you expect on a local area network (LAN).
- Existing background load on the network or the machines being used for testing
- 100Mb/sec was negotiated by the card / switch instead of 1Gb/s. Maybe due to errors on the link or excessive cable length
- CPU might not be quick enough. Note that single core performance is important for the network test. Multiple cores don't help when you have only a single instance of the test running.
- PCIe bus connecting the network card to the CPU might be too slow
- Cabling problems. e.g. using CAT5 instead of CAT6
- Wrong device driver is loaded up for the network card (NIC)
- Poor TCP/IP settings. For example jumbo Ethernet frames (MTU), PCI burst transfer sizes.
- If the NIC supports processing offload. (called TCP offload engine or TOE)
- Routers / switches / Firewalls are not setup correctly or were never designed for the required speed.
- The connection is high latency due to the machines being far apart, or routing problems causing the wrong route to be selected.
- Low level physical errors on the link, data corruption, electrical issues, re-transmisions, EMI.
- If you are using WiFi, then radio interference, congestion, low signal levels & reflections, can all cause problems.
Tools, like WireShark & NetStat, can help in getting to the bottom of networking problems & to monitor link errors.
On older laptops network speeds are usually limited by the PCMCIA bus speed. You may have a 100 MBps network card, but the PCMCIA bus will not allow transmission rates much above 10 MBps.
You may have to set up a rule allowing access on the port used by the network test. If you don't have direct control over the firewall, you'll have to contact your network administrator. The port number used by the test can be found in the network test dialog. In WIndows 10, you should be prompted automatically to allow PerformanceTest through the firewall at the start of the test. 3rd party firewalls might need to be manually configured.
The most likely causes are:
- You forgot to click on the "Go" button on the server
- In the PerformanceTest Advanced network test window (on the client/sending PC), the IP address entered is incorrect or the port numbers on the client and server PC's do not match. The same port number must be used on both PC's. The IP address of the server PC, must be entered on the client PC.
- A firewall (eg. Microsoft XP firewall or Norton Internet Security Firewall) is turned on for one or both of the PC's LAN connections and this is blocking a connection. Solution: modify the firewall rules to allow this address, port and protocol through the firewall or switch the firewall off (if appropriate).
- The network cards are not working. You should check in device manager that your Network cards are shown as "This device is working properly".
Note: To test connectivity between the Client PC and the Server PC try the following: Open a "Command" window on the Client side PC by selecting "Start", "Run", type in "Command". Once you have the "Command" window open, type "ping <IP-Destination>", substituting <IP-Destination> for the IP address of the Server side PC.
When the Client computer graph shows that nearly the entire bandwidth is utilized for the full test duration of the send session and the receiver shows that after a number of seconds into the test a drop from nearly 100% utilization to 0, the most likely cause is that a router between the PC's is dropping UDP packets.
UDP is not rate adaptive (basically packets are pushed out as quickly the PC can push them out with no consideration whether the packet was received), unlike TCP. A router between the PC's could become congested and hence start dropping the UDP packets, and remain congested until the end of the test (This is of course more likely if the router is a lower end router or there are other users on the network). Depending on your router, you may be able to get UDP statistics on the 'in' and the 'out' ports to confirm this. You could also try connecting the 2 PC's directly (depending on what you are trying to test).