Winsock Stress Test - Name Resolution (Compact 7)
3/12/2014
The Winsock Stress Test strains Winsock and networking functionality by performing a large number of socket operations. The socket operations performed by this test may also stress the remainder of the networking stack, for example, when receiving and sending large amounts of data.
Resolves computer names into addresses and addresses into computer names. You can specify the number of resolutions to perform. You can also specify a list of computer names or addresses to resolve.
The test carries out resolutions in two concurrently running threads. One thread resolves computer names to addresses and the other thread resolves addresses to computer names.
The test will displays the results of the resolutions after the test completes.
Test Prerequisites
Your device must meet the following requirements before you run this test.
There are no hardware prerequisites for Name Resolution Winsock Stress Test.
The following table shows the software requirements for the Name Resolution Winsock Stress Test.
| Requirements | Description |
|---|---|
netall.dll |
Module that provides functions that generate random numbers, output data, and parse command lines. The netall.dll file must be located in the same directory as the test. |
ghstres2_vx.exe |
Name Resolution Winsock stress test application |
Subtests
This test has no subtests.
Setting Up the Test
This test has no additional requirements beyond the standard test environment setup.
Running the Test
The Winsock Stress Test does not use the Tux test harness. You must run this test manually via Platform Builder's command line prompt.
The Winsock Stress Test has the following command line options, which you can display via the command: s ghstres2_vX.exe /?
ghstres2_vX [-f Frequency] [-m Milliseconds] [-r Reps] [-a IPAddress] [-n HostName] [-ipv IPVersion] [-s] [-l]
| Parameter | Description |
|---|---|
f: |
Number of interations to perform before displaying status (default: 10) |
m: |
Number of milliseconds to wait between iterations (default: 0) |
r: |
Number of reps to execute the test (default: 0) |
a: |
IP address of a host to resolve into a name |
n: |
Name of a host to resolve into an address |
s: |
Flag to perform Resolution Test against primary DNS server |
ipv: |
Flag to force IP Version. Bypassed by -a. [values: 4 or 6] (default: AF_UNSPEC) |
l: |
Force the usage of legacy Get Host Stress - ghstres2.exe |
NOTE Multiple addresses and names can be given but they must be separated with semi-colons. Up to 5 names/addresses
In addition, you can specify the following command-line options to modify the behavior of the test. Add one of the command-line parameter to:
Parameter Description
-z Redirect output to the console
-fl <filename> Redirect output to a file
The following table shows the test cases for the Name Resolution Winsock Stress Test.
s ghstres2_vx -f100 -r1000 -n loopback;localhost The following command line on the Windows Embedded Compact powered device resolves two computer names 1000 times using the IPv4 gethostbyname function.
s ghstres2_vx -f100 -r1000 -n localhost -a 127.0.0.1 The following command line on the Windows Embedded Compact powered device resolves a computer name and an IP address 1000 times using the IPv4 gethostbyname function and gethostbyaddr function.
s ghstres2_vx -f100 -r1000 -n localhost -a 127.0.0.1;::1 The following command line on the Windows Embedded Compact powered device resolves computer names and IP addresses for both IPv4 and IPv6 1000 times using the getaddrinfo function and getnameinfo function.
Verifying the Test
During the running of the test, there should not be any consistent failures. At the end of the test a summary of the tests run will be displayed.
Troubleshooting the Test
If you specify the computer names or addresses, ensure that they are correct and reachable.
Ensure that the device has an network connection.
If the resolutions fail, you can try adding some delay between iterations.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.