Chrome slows done when another hdd has 100% active time and avg. response of 1000mm
Reported by
seelbrea...@googlemail.com,
Sep 4 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Example URL: everyone Steps to reproduce the problem: 1. Start an Download which saves to my toshiba DT01ACA300 which is Disk 1 D: (chrome is installed on the SSD which is on Disk 2 C:) 2. When the download has startet after some time the Disk gets 100% activity and avg response time of 1000-5000ms 3. Start browsing and wait..... What is the expected behavior? Chrome shouldn't be slow when another Disk is used too its fullest extent. May it be a problem with the disk or not. What went wrong? It seems like chrome is using or waiting for the Disk D:\? To get free active time so that it can show the website Did this work before? N/A Chrome version: 52.0.2743.116 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Sep 4 2016
Issue 644015 has been merged into this issue.
,
Sep 7 2016
It appears we're waiting for the cache to return things. Ultimately, Chrome does need to hit disk for things, so if you disk is totally unresponsive, you'll probably be unhappy. I think, for the most part, we assume that disk is always faster than network. There's been some chatter about adding a bunch of complexity to account for this not being true, but I don't know if there's been any movement here. Tossing over to cache folks.
,
Sep 8 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by seelbrea...@googlemail.com
, Sep 4 2016170 KB
170 KB View Download