Test Cases for the Winsock Performance Test
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
By default, each test case for the Winsock Performance Test runs once for each buffer or packet size specified in a predefined list of buffer or packet sizes. For TCP, the following buffer or packet sizes are tested: 16, 32, 64, 128, 256, 512, 1024, 1460, 2048, 2920, 4096, and 8192 bytes. For User Datagram Protocol (UDP), the following buffer or packet sizes are tested: 16, 32, 64, 128, 256, 512, 1024, and 1460 bytes.
By default, a test case sends each packet or buffer 10,000 times for throughput tests and 100 times for ping tests.
The following table shows the test cases for the Winsock Performance Test. For more information about specifying the buffer size, number of iterations, and other settings from the command line, see Command Line Parameters for the Winsock Performance Test.
| Test case | Description |
|---|---|
1001 |
TCP Send Throughput Uses the Winsock send function to send data over TCP from the Perf_winsock2.dll client to the server, which receives data by using the Winsock recv function. This test case expresses send throughput in Kbps. The test case measures the time required to send an amount of data, not including protocol headers, determined by the specified buffer size and number of iterations. TCP connection setup and tear-down times are ignored when evaluating throughput. The test case measures CPU use at the client. A value of 100% indicates that the CPU is fully used. |
1002 |
TCP Recv Throughput Uses the Winsock recv function to receive data over TCP at the Perf_winsock2.dll client from the server, which sends data by using the Winsock send function. This test case expresses receive throughput in Kbps. The test case measures the time required to receive an amount of data, not including protocol headers, determined by the specified buffer size and number of iterations. TCP connection setup and tear-down times are ignored when evaluating throughput. The test case measures CPU use at the client. A value of 100% indicates that the CPU is fully used. |
1003 |
TCP Ping Instructs the client and server to run a TCP ping test where the Perf_winsock2.dll client uses the Winsock send function to send a TCP packet, or set of packets making up a specified buffer size, to the server. The server replies by sending the same packet to the client. This test case expresses TCP ping delay in milliseconds (ms). The test case measures the average time elapsed between the client sending a packet and receiving a response from the server. TCP connection setup and tear-down times are ignored when evaluating delay. |
1004 |
TCP Send Throughput Nagle Off Runs test case 1001 with the Nagle algorithm disabled. |
1005 |
TCP Recv Throughput Nagle Off Runs test case 1002 with the Nagle algorithm disabled. |
1006 |
TCP Ping Nagle Off Runs test case 1003 with the Nagle algorithm disabled. |
1007 |
UDP Send Throughput Uses the Winsock send function to send data over UDP from the Perf_winsock2.dll client to the server, which receives data by using the Winsock recv function. This test case expresses send throughput in Kbps. The test case measures the time required to send an amount of data, not including protocol headers, determined by the specified buffer size and number of iterations. The test case measures CPU use at the client. A value of 100% indicates that the CPU is fully used. |
1008 |
UDP Send Packet Loss Sends data over UDP from client to server at different rates to discover when packet loss occurs. For each rate, this test case expresses packet loss by showing the percentage of packets sent that were received by the server. The test case measures CPU use at the client. A value of 100% indicates that the CPU is fully used. |
1009 |
UDP Recv Throughput Varies the send rate from the server to discover the maximum rate at which the client can receive UDP packets with no packet loss. This test case expresses in Kbps the maximum rate at which the client can receive data in UDP packets, not including protocol headers. The test case measures CPU use at the client. A value of 100% indicates that the CPU is fully used. |
1010 |
UDP Recv Packet Loss Sends data over UDP from server to client at different rates to discover when packet loss occurs. For each rate of data transmission, this test case expresses packet loss by showing the percentage of packets sent that were received by the client. The test case measures CPU use at the client. A value of 100% indicates that the CPU is fully used. |
1011 |
UDP Ping Instructs the client and server to run a UDP ping test where the Perf_winsock2.dll client uses the Winsock send function to send a UDP packet, or set of packets making up a specified buffer size, to the server. The server replies by sending the same packet to the client. This test case expresses UDP ping delay in milliseconds (ms). The test case measures the average time elapsed between the client sending a packet and receiving a response from the server. |