initial network access time undercounted in performance tools
Reported by
ocie.mit...@gmail.com,
Nov 27
|
|||||||||
Issue description
Chrome Version : 70.0.3538.77
OS Version: OS X 10.13.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: OK
Firefox: N/A
IE/Edge:
What steps will reproduce the problem?
1. start the attached expressjs app (serves up a simple html page with 1 stylesheet and artifical 2 second delay on each request)
2. open "localhost:3000"
3. compare the loading time of the initial html file in the network tab with the network view in the performance tab
What is the expected result?
The performance tab should indicate that it took over 2 seconds to retrieve the initial document
What happens instead of that?
The performance tab only shows a few milliseconds were used for the initial document.
Please provide any additional information below. Attach a screenshot if
possible.
The network tab correctly shows that it takes over 2 seconds to retrieve the initial document. Also, the performance tools correctly show that it takes over 2 seconds to retrieve the css document.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36
,
Nov 27
,
Nov 27
Network view in devtools shows only 8ms to retrieve http://localhost:3000/
,
Nov 28
,
Nov 28
Thanks for filing the issue... Tried to reproduce the issue on reported chrome using Mac 10.13.6. Attaching screencast for reference. Steps: ----- 1. Launched reported chrome 2. Downloaded given slowserver.zip and launched through local server 3. Opened Dev tools >> Network and Performance tabs As we have not seen html file and on network tab observed 13ms and performance tab 1.1ms @Reporter: Could you please check the attached screen cast and let us know if anything missed from our end and verify this issue on chrome beta 71.0.3578.62 you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists. Thanks..!
,
Nov 28
Sorry, I should have included a bit more info on the test application. This is a nodejs app which introduces an artificial delay in serving the '/' and '/somefile.css' content. You will need nodejs to run the app. To start it, run 'npm install' and then 'npm start'. After that, navigate to http://localhost:3000.
,
Nov 28
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 28
I tried this in Chrome canary (Version 72.0.3624.0 (Official Build) canary (64-bit)) and I see the same issue.
,
Dec 4
I can repro. Thanks for the report. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 Deleted