localhost latency tests work, over network they do not...
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.9k
- Forks
- 406
- PR merge metrics
- No merged PRs in 30d
Description
might be a firewall issue or a mixed client issue but I can't get the latency (tcp or http) tests to work:
client (mac), server (windows), both compiled from master.
over network:
client$ ./ethr -t l -c $server -p tcp
Avg Min 50% 90% 95% 99% 99.9% 99.99% Max
Ethr done, duration: 10s.
server$
Starting TCP Latency test from $client
[RemoteAddress] Proto Bits/s Conn/s Pkt/s Latency
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
[ 47.35.241.31] TCP 0.000ns
Ending Latency test from $client
when local:
$server ethr.exe -t l -c localhost -p http
Avg Min 50% 90% 95% 99% 99.9% 99.99% Ma
739.243us 0.000ns 671.600us 999.300us 1.058ms 3.920ms 31.285ms 31.285ms 35.1
0ms
918.964us 0.000ns 938.100us 1.041ms 1.403ms 9.763ms 31.241ms 31.241ms 31.28
ms
940.411us 0.000ns 945.100us 1.013ms 1.871ms 10.739ms 31.317ms 31.317ms 31.95
ms
1.022ms 0.000ns 956.800us 1.251ms 1.843ms 13.164ms 29.524ms 29.524ms 31.249
s
876.940us 0.000ns 930.000us 1.008ms 1.308ms 8.363ms 30.277ms 30.277ms 30.74
ms
882.817us 0.000ns 855.100us 1.015ms 1.468ms 11.677ms 31.335ms 31.335ms 34.22
ms
809.564us 0.000ns 898.200us 999.000us 1.154ms 6.028ms 31.250ms 31.250ms 34.1
9ms
716.782us 0.000ns 431.600us 993.700us 1.017ms 3.718ms 31.238ms 31.238ms 32.1
5ms
836.949us 0.000ns 876.900us 1.000ms 1.363ms 7.959ms 31.213ms 31.213ms 38.08
ms
862.278us 0.000ns 912.400us 1.001ms 1.165ms 8.436ms 30.663ms 30.663ms 33.65
ms
880.880us 0.000ns 890.700us 1.007ms 1.446ms 8.944ms 30.746ms 30.746ms 38.56
ms
Ethr done, duration: 10s.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the TCP and HTTP latency commands shown for the macOS client and Windows server, comparing network runs with localhost. Trace the latency-test entry points and protocol-specific handling to find why remote runs report 0.000ns, then verify that cross-network TCP and HTTP tests produce latency statistics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100