Default Number of Tests per Probe Type (N2N)
Queue Management Concept
While trying to execute the tests configured by the users and scheduled on the system, the scheduler will follow following rules:
- pick first tests that are earlier in Next Execution time
- give priority to Mesh tests in Meshes that are left to complete (see Mesh tests for details)
- give priority to One shot tests over scheduled tests
- Check probe execution capability and:
- do not allow to run 2 different test types at the same time on same probe
- allow running simultaneous tests on same probe only in same test run (once a probe is running it cannot be used for other tests even if this is same test type.
- max total number of tests per probe depends on probe type and test type. See table below.
How is a Probe Identified
A probe is by default identified by its Serial Number. If this is empty and Use probe Management IP is defined (should be default), probes with same management IP will be identified as sharing same hardware.
This configuration is useful when using several interfaces on same probe and allows to gave probe control management.
Maximum number of simultaneous tests per probe type and test type
Table below displays the number of max concurrent tests that are allowed on one probe to run.
These metrics can be modified by advanced administrator - contact support for advise and recommendations.
| Software | XR2000 / VM | XRPi | Pi4 | XR Docker | XR-E1S | XR VM | XR3000 | IxProbe, IxTap, IxByPass * | |
|---|---|---|---|---|---|---|---|---|---|
| Adaptive Video | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Adaptive video with network quality | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Citrix | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| COS line qualification | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| DNS Response Time | 200 | 200 | 20 | 20 | 20 | 20 | 200 | 20 | 20 |
| Exchange_traffic | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Flash RTMP | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| FTP Response Time | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| HTTP Test | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| HTTPS Test | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| Multicast Video over RTP | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Netflix | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Network KPI | 100 | 500 | 50 | 50 | 50 | 50 | 500 | 50 | 50 |
| Network KPI 3 COS | 5 | 125 | 12 | 12 | 12 | 12 | 125 | 12 | 12 |
| Network KPI Advanced | 80 | 320 | 32 | 32 | 32 | 32 | 320 | 32 | 32 |
| Network KPI bidirectional | 25 | 250 | 25 | 25 | 25 | 25 | 250 | 25 | 25 |
| Network KPI Low Bandwidth | 50 | 300 | 50 | 50 | 50 | 50 | 300 | 50 | 50 |
| Network KPI to->from | 100 | 500 | 50 | 50 | 50 | 50 | 500 | 50 | 50 |
| Network loss performance | 10 | 10 | 10 | 10 | 11 | 13 | 10 | 13 | 10 |
| POP3 Response Time | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
|
RTSP |
1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| SIP Response Time | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| Skype4B Traffic | 20 | 80 | 8 | 8 | 8 | 8 | 80 | 8 | 8 |
| Skype4B Traffic from->to | 40 | 160 | 16 | 16 | 16 | 16 | 160 | 16 | 16 |
| SLA Traffic Mix bidirectional | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| SMTP Response Time | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 |
| Speedtest bidirectional | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest from->to | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest from->to 2 COS | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest from->to 3 COS | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest from->to 4 COS | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest from->to 5 COS | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest to->from | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Speedtest from->to with KPI | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Response Time | 200 | 200 | 20 | 20 | 20 | 20 | 200 | 20 | 20 |
| TCP Throughput Advanced | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Throughput bidirectional | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Throughput from->to 1 stream | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Throughput from->to N streams | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Throughput Optimized Window size | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Throughput to->from 1 stream | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| TCP Throughput to->from N streams | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Teams Cloud Call | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Teams WAN Call | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Traffic Mix - HTTP - Video - Voice | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput Advanced | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput bidirectional | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput from->to | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput from->to - 4 COS | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput from->to N streams | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP throughput from->to with delay/jitter | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput to->from | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| UDP Throughput to->from N streams | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Video Stream | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Voice bidirectional | 10 | 200 | 20 | 20 | 20 | 20 | 200 | 20 | 20 |
| Voice from->to | 50 | 500 | 50 | 50 | 50 | 50 | 500 | 50 | 50 |
| Voice N pairs - UDP Data bidirectional | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Voice N Pairs bidirectional | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Voice N Pairs Unidirectional | 1 | 10 | 1 | 1 | 1 | 1 | 10 | 1 | 1 |
| Youtube | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
| Zoom meeting | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 |
* The maximum number of simultaneous tests with the Trusted Subnet mode enabled is restricted to one.