Open laeti-tia opened 5 years ago
Just so you re aware, when OWAMP results are archived in esmond, the statistics summary calculates many of the common percentiles used in "jitter" measurements for precisely this type of use case. You an see an example at http://lbl-pt1.es.net:8085/esmond/perfsonar/archive/087d7070d7164e25884348ee2a6948fb/histogram-owdelay/statistics/0?time-range=600 or below:
{
"ts": 1547479931,
"val": {
"standard-deviation": 0.03788716801240232,
"median": 28.34,
"maximum": 28.38,
"minimum": 28.21,
"mode": [
28.34,
28.36
],
"percentile-75": 28.35,
"percentile-25": 28.29,
"percentile-95": 28.36,
"variance": 0.0014354375000000014,
"mean": 28.321749999999998
}
}
The calculations happen at the esmond layer. The percentiles are not configurable at the moment but look closer to what you need.
There is interest from the GÉANT project collaborations to store and display trends of jitter measurements. This is an important metric pour real-time applications (audio, video and some HPC applications).
owping
is reporting a jitter calculation with every run of latency measurements. The delay variation is calculated between the 95th percentile and the median (or 50th percentile).owping
can also report other percentiles, so maybe we could make the jitter calculation configurable so to match different use cases.Here are some
owping
output examples:Default jitter calculation and output of additional percentiles: