Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2013-09-03 | 1.8 kB | |
JNodeToNodeClockSkew-1.2.2-src.zip | 2013-09-03 | 126.2 kB | |
JNodeToNodeClockSkew-1.2.1-src.zip | 2013-08-23 | 126.1 kB | |
JNodeToNodeClockSkew-1.1.2-src.zip | 2013-05-08 | 65.1 kB | |
Totals: 4 Items | 319.3 kB | 0 |
Project Home
About the JAVA Node-to-Node Clock Skew Tool
This tool allows you to resolve clock differences between two nodes, often to 20 microseconds. It is designed to be used just before or just after intra-node experiments to allow the user (or program) to determine clock differences that may be used to calibrate intra-node event times.
The tool can run from the command-line or run under program control.
Change History
1.2.2
- Fixed error in computation of one-way throughput
1.2.1
- Added the -waitSecs option to specify a maximum wait time for the remote end
- Fixed a hang problem when using large TCP buffer size
1.2
- Added a -tcp option (also -send and -listen) to use TCP instead of the default UDP.
- Added a pingPongBandwidthInBytes to measure effective bandwidth.
- Added a computedMaxBandwidthInBytes to predict max bandwidth.
- Added a -bufSize parameter to set the size of messages being exchanged.
1.1.2
- Added a SkewCorrectionListener
- Reworked SkewCorrection to have bean methods
- Added methods TimeCorrection.writeLocallyComputedCorrection() and TimeCorrection.writeRemotelyComputedCorrection() ; removed old writeCorrection() method
1.1.1
- Fixed minor bug in TimeCorrection that failed to report an error if the directory for the corrections could not be created.
1.1
- Added ability to use two separate ports for send and receive
- Simplified the way the nanosecond clock was used. Improved accuracy from about 6 us. to about 0.3 us. on my test system with 1000 ns clock resolution.
- Simplified the way a local correction instance is run in its own thread.
1.0
- Initial