| Age | Commit message (Collapse) | Author |
|---|
|
As it turns out, I was misreading the algorithm for calculating the RPM
based upon the measurements taken during execution. This patch fixes
that mistake and also (starts) renames "RTT" as "measurement" (those are
technically a better nomenclature according to the spec.)
|
|
There was an error in prior versions when calculating the RPM in the
presence of reused connections because invalid time values were being
compared. This patch fixes that error.
|
|
Refactor RPM calculations to make them more reusble. Enable (perhaps
temporarily) probe calculations on the saturated connections. This
change is to check whether this makes our RPM calculations match the
ones generated by Apple's native client.
|
|
This patch begins the work on updated RPM calculations using
the httptrace infrastructure. Because we are still not able
to break out the TLS handshake time due to upstream bugs, there
are some workarounds in place. However, the numbers appear much
more sane.
|
