| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This patch adds support for logging the underlying RTT and Cwnd of the
TCP connection used when doing probes. More work to follow in order to
add support for this information on Windows and Darwin.
|
|
We never really implemented it any way!
|
|
There were several places where boilerplate language was left in the
license block at the top of files containing source.
|
|
With this patch, data logging now supports reporting the moving
average of upload/download throughput as saturation is pursued.
|
|
|
|
Besides work to complete the support for v2 of the RFC, this patch adds
support for logging each of the probe results to a CSV file
(--logger-filename).
|
|
|
|
|
|
This is a WIP for supporting v2 of the RPM spec.
|
|
Cipher comparison on non-AES hardware
|
|
Compares measurement capabilities (for AES vs CHACHA ciphers) on an older "low-end" router that does not have AES hardware support. More information in README.md
|
|
Besides running golines (for the first time in a while now that
the tool supports generics), this commit removes punctuation and
newlines from Errorf parameters -- something that gofmt does not
like (I never knew!).
|
|
[Feature] Add extendedstats support for Windows
|
|
The added support has similar stats to getTCPInfo for linux.
Signed-off-by: Will Hawkins <[email protected]>
|
|
Now that there is support for GetTCPConnectionInfo on macOS, we can
re-enable extended stats on the macOS platform!
|
|
@moeller1 requested additional stats on the *nix platforms. Subsequent
patch will enable the same statistics on macOS.
|
|
In the conditionally compiled code on Windows, there was a missing "fmt"
import that broke the build. This patch rectifies that problem.
|
|
Timeout patch
|
|
|
|
|
|
IncorporateConnectionStats
Errors as a result of failed type assertions in
IncorporateConnectionStats were caught/logged but there was no
function-termination control flow associated with these error
conditions. As a result, control would continue and cause problems. This
patch fixes that.
|
|
Update Dockerfile and .gitignore
|
|
Disable extendedstats for Darwin builds
|
|
|
|
The Darwin golang.org/x/sys/unix package does not contain a TCPInfo
struct, which causes the project not to compile on macOS systems.
|
|
|
|
(Unused containers accumulate if you don't --rm.)
|
|
Now that we are conditionally building parts of the source code so that
we can use *nix's platform support for TCPInfo, it is hard to make sure
that I have all platforms working right at the same time.
@Schickendantzj helped debug this error this morning.
|
|
|
|
|
|
|
|
On *nix platforms, there is now a `-extended-stats` option that will
print out some extended statistics for the test. The statistics are
based on information gleaned from the `TCP_INFO` of the underlying TCP
connections. What is implemented so far is just a proof of concept of
the extended stats that could be calculated. Depending on what users
want, we can add additional extended statistics.
|
|
Now there is functionality for conditionally supporting GetTCPInfo
depending on the platform. If the platform supports it, then the client
can call utilities.GetTCPInfo. In the case that the platform does not
support the GetTCPInfo function call, the result is an error of the type
`NotImplemented`.
|
|
This will only work on *nix systems. Code that displays information
in this PR is only exemplary -- I am sure that there are better
places in the code to display it!
|
|
Fixes #21
|
|
1. A misleading comment was corrected.
2. A typo was fixed.
|
|
Previously the code relied on the fact that the go runtime would wake up
the saturation go function at exactly 1 second intervals, as we asked.
With this change, the code takes into account any minor fluctuations in
that time when calculating the throughput in an interval. I hope that
this change is an improvement.
|
|
|
|
1. Create a separate package to handle the config information.
2. Move the saturate functionality into the rpm package.
3. Do general renaming/refactoring so that we are consistently
saying measurement and not RTT (this nomenclature is more consistent
with the standard).
|
|
Per a (to-be-released) update from the spec, the time for a DNS lookup
is no longer considered to make up a portion of the RPM.
|
|
Switch from calculating "difference" as percent difference to calculating
the difference as percent change.
|
|
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.
|
|
|
|
The first set of raw data and a tool for munging it into csv files. The
data look promising but there are a few things that we need to address.
|
|
* 'main' of https://github.com/richb-hanover/goresponsiveness-1:
[Bugfix] Null pointer dereference when debugging disabled
|
|
When there is no debugging enabled, there was a null pointer dereference
as a result of invoking `saturate` with a null pointer to a `debug.Debugging`
structure.
|
|
* 'main' of https://github.com/richb-hanover/goresponsiveness-1:
Upgraded RPM Calculation Support (Take 1)
Make Traceable Interface and Refactor Debugging
Fully support self-signed certificates (and add debug levels)
|
