Test type general description
You must be aware of scheduling tests too frequently for the probe. When scheduling tests the user needs to be aware that the test duration is more than the configured “traffic duration”. The total test duration will include time to setup the test, specifically time taken for the Hawkeye Server sending test configuration commands down to the endpoints, test setup on the endpoints, endpoints calculation of test statistics following test completion, endpoints then sending results back to Hawkeye Server, and the Hawkeye Server finally recording resulting test metrics in the Results database. One way to know how long a test takes is to schedule a test every 10 minutes, then see the timestamp in test results which reflects the start time, plus traffic duration plus processing overhead to get to test metrics stored in the Results database
This section explains the following topics:
Understanding Node to Node Metrics
Testing Throughput Using TCP or UDP