Slower load times for navigation type TYPE_BACK_FORWARD, gap between fetch start and domainLookupStart
Reported by
dani...@lucidchart.com,
Dec 7
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: I am unable to reproduce locally. This is from aggregated metrics we collect in production. What is the expected behavior? Load times consistent with Chrome 68 and previous versions. What went wrong? When Chrome 69 was released (and still with Chrome 70), we noticed that our users using Chrome 69 experience much slower load times compared to Chrome 68. This is especially noticeable when looking at our slowest customers (95th percentile and higher.) Load times for these users are as much as 20-40% higher. What I have gathered: * For these users, they experience a large gap between the fetchStart and DNSLookupStart. This is for users with or without our service worker installed. This large gap does not account for the entire amount of additional load time. * We are only seeing this for users with navigation type 2 (TYPE_BACK_FORWARD) (~7.5% of our loads.) In the linked document are some graphs: https://docs.google.com/spreadsheets/d/1v7Rw6ZgR8-i4EP1E7LrnCP68wl9Btxku5dMydO_H2XQ/edit?usp=sharing Did this work before? N/A Chrome version: 69 Channel: n/a OS Version: Flash Version: Please let me know what data, etc... you need.
,
Dec 12
,
Dec 13
Thanks for filing the issue! @Reporter: Could you please try to test this issue on latest chrome stable# 71.0.3578.98 and let us know if the issue still persists. If reproducible on latest stable, please provide sample Test File/URL that reproduces the issue which help in further triaging it in better way. Note: You can download latest chrome stable from URL: https://www.chromium.org/getting-involved/dev-channel Thanks!
,
Dec 14
I am not able to reproduce this locally. Looking at our stats from production, I still see the slower load times being reported for users using Chrome 71. The slower load times are characterized by slower overall load times, a gap between fetchStart and dnsLookupStart, and only happens to users with navigation type 2. Is there anything about 71.0.3578.98 in particular that could improve this?
,
Dec 14
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
,
Dec 14
Actually perhaps I spoke too soon. Overall load times for nav type 2 seem improved in Chrome 71, however, the gap between fetchStart and dsnLookupStart still exists.
,
Dec 14
It looks like the overall situation is much improved for Chrome 71. The majority of our users are still on Chrome 70, hopefully in the next week or so I can say more definitely.
,
Dec 20
,
Jan 7
,
Jan 7
We can close this ticket. Now that most of our users are on Chrome 71, it's apparent that Chrome 71 has similar performance to Chrome 68 in this regard.
,
Jan 7
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
,
Jan 8
danielj@ Thanks for the update. As per comment #10, marking this issue as WontFix as the reporter has confirmed. Please feel free to raise a new bug if any issues are observed on the latest Chrome builds. Thanks.. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by susan.boorgula@chromium.org
, Dec 9