-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dbw network-server-latency
is 0 for localhost on windows
#15160
Comments
I collected the Notably, the only variant that has connectStart/End timing is Windows Here's what I got: Windows
Windows
Mac
Mac
|
It's very unexpected that we only get connection timing from one of the above variants. Looking closer at that one, 300ms seems huge for connecting to a localhost server. Let's see how long just a direct request takes: Windows,
Windows, python server:
Mac:
(good for mac) |
I've found that on Windows, the first request for a server using Node 16 takes an extra 300ms. Subsequent ones are fine. Node 18 seems fine. Using Node 18, the connectStart/End times are now -1 like all the other variants 👀
None more enlightened as to the root cause (why do we get -1 here?!), but I suppose we could update to Node 18 in CI to resolve this. |
This is addressing the current dbw smoke fixture for Windows on the main branch. #15113 added this assertion for
network-server-latency
to be>0
on dbw. It's now failing in main branch.On Windows:
The RTT estimate for localhost is ~300ms. This Is huge for localhost. Bad estimate, breaks how
estimateResponseTimeByOrigin
works and returns zeros.So then for many samples, we get
ttfb - rtt < 0
, which means we get 0.On Mac:
The RTT estimate is 0.05 ms, which is why we get a >0 latency here (as expected).
The text was updated successfully, but these errors were encountered: