Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This is a study of the differences (if any) of the measurements from pinger.slac.stanford.edu (a single (raw bare hardware non-virtual) Linux host (Dell PowerEdge 2650) running the PingER Measurement Agent (MA)  measuring the ping Round Trip Times (RTTs) to  and pingervm (AKA  dhcp-nebula-124-66.slac.stanford.edu a Nebulr KVM Virtual Machine) and vice versaNebula KVM Virtual Machine with floating addresses) MA measuring the ping Round Trip Times (RTTs) to hosts worldwide and between pinger and pingervm. Hencefiorth we refer to ping requests from pinger to pingervm as pinger to pingervm or pinger>pingervm and ping requests from pingervm to pinger as pinger to pingervm or pingervm>pinger. Both pinger and pingervm are located on the second floor of Building 50 (the computer center) at SLAC.  The traceroutes between the two machines are seen here.

The measurements were made from February 26th 2015 and March 3rd 2015. Every ~30 minutes a burst of 10-30 (10 if no loss else up to 30 until 10 ping responses were received) ping requests  was sent by the MA to the  target. The ping packet size was 100Bytes, the ping requests in the burst were separated by 1 second. The number of pings between pinger and pingervm was ~6000.

Below we look at a statistical analysis  of the results for pings from pinger and pingervm to the World, to N. America, Europe and between pinger and pingervm.

To World (excluding SLAC targets).

The following tables are from pingtable.pl

...

PingER non VM measurement agent
Tickmin25th%avgmedian75th%90th%95th%maxiqrstd dev# pairs
Mar201523.312178.346239.329211.152293.499339.425379.947780.659115.153104.510107
Feb201522.689176.167241.608212.435295.448326.637362.350803.815119.281110.212112

...

PingER VM Measurement agent
To Europe
Tick
# pairs
Mar2015151.017162.965176.121173.904185.921199.620208.584208.58422.95617.58614

To N. America

...

PingER non VM measurement agent
Tickmin25th%avgmedian75th%90th%95th%maxiqrstd dev# pairs
Mar201523.312.54.89062.04279.31579.31579.31579.315.28.6783

...

And plots of the time series appears as below (spreadsheet)?

Looking at the above manually scaled plots of pinger>pingervm and pingervm>pinger it is apparent the RTTs from pinger to pingervm are > pingervm to pinger. Looking at the average, standard deviation, median and IQR tables and the differences between pinger as the monitoring site and pingervm as the monitoring site, we see in tabular form (where the average errors are +- (stdev(pinger>pingervm)+stdev(pingervm>pinger)) and the median errors are +- (IQR(pinger>pingervm) + IQR(pingervm>pinger)). the Probabilities are those that the pinger>pingervm and pingervm>pinger distributions are the same (assuming normal distributions).

...

By looking at the cumulative distributions we can get the Median differences probability.

Minimum RTT distributions between pinger and pingervm

We focus on the minimum RTT since that is least affected by queuing etc.

Image Added