The test configuration options are available when creating a custom test.
Download test: Select this option to do a download test, i.e. from server to the client.
Upload test: Select this option to do an upload test, i.e. from client to server.
Download Sockets/Threads: Enter the number of sockets and threads per socket for the download speed test. The number of sockets needed test the connection to the maximum capacity will be dictated by the latency of the connection. As a rule of thumb, for every a 10ms of latency, the HiSpeed test will require 20 sockets with 1 thread, therefore a 40ms latency will require 80 Sockets one thread or 40 sockets with two threads. For efficiency of the test it is advisable to use one thread per socket.
Upload Sockets: Enter the number of sockets for the upload high speed test. The number of sockets needed test the connection to the maximum capacity will be dictated by the latency of the connection. As a rule of thumb, for every a 10ms of latency, the HiSpeed test will require 20 sockets therefore a 40ms latency will require 80 Sockets.
Thread priority: select this option to enable the maximum thread priority. See notes below.
Number of RTT tests: This parameter defines the number of round trip time measures to be tested. This is a true TCP trip time not a ping measure which is not as accurate. Trip time is a very important measure for TCP throughput. Configuring multiple trip measures allows the test to assess trip time variance. A high variance is the first indicator of poor connection quality.
Test duration: This parameter defines the amount of time you want the download and upload tests to last. This is defined in milliseconds. The limit is 90 seconds (90000 milliseconds).
Notes. When testing high bandwidth pipes at 1Gbps over higher latency network connections then the volume of sockets needed to generate the payload to sustain the maximum capacity may exceed the ability of the PC client.