New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 675960 link

Starred by 1 user
Status: Duplicate
Merged: issue 677839
Owner: ----
Closed: Jan 2017
Cc:
█ kapishnikov@chromium.org
█ rdsmith@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Performance issue opening large (10 MB) files (txt, json etc.) files in Chrome

Reported by gjerm...@gmail.com, Dec 20 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Example URL:
http://norvig.com/big.txt

Steps to reproduce the problem:
1. Open Developer Mode - Network Tab
2. Open the URL http://norvig.com/big.txt
3. Look at the time bars in the Network Console

What is the expected behavior?
It should load almost immediately

What went wrong?
It takes several seconds to download/render the text file on screen.

Using Firefox it takes 0.10 sec. (I am on a 1000mbit connection.)

Chrome is in general very slow when it comes to downloading/viewing large responses. I discovered the error when loading some JSON responses from localhost. Downloading a 4.5 MB JSON from localhost takes 2.44 sec using Chrome.

It takes 100 ms with Firefox.

Did this work before? N/A 

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0
2016-12-20_1510.png
33.6 KB View Download

Comment 1 by kapishnikov@chromium.org, Dec 21 2016

Cc: kapishnikov@chromium.org rdsmith@chromium.org
Components: -Internals>Network UI>Browser
It looks that the bottleneck is in the content rendering. Indeed, it takes more time to load the file from the network (confirmed with wireshark) but it happens because the renderer process doesn't pump out the data fast enough. As the result the TCP window is exhausted and the transmission is blocked.

Could somebody from the UI team to look why the rendering takes more time than expected?

Adding rdsmith@ who helped me to diagnose the problem.
SlowRendering.png
15.8 KB View Download
tracing.png
121 KB View Download

Comment 2 by rdsmith@chromium.org, Dec 21 2016

Components: -UI>Browser Blink>Loader
I don't think this is about browser UI; shifting tentative component assignment to Blink>Loader.

Comment 3 by woxxom@gmail.com, Dec 22 2016 

This is partially caused by complex font rendering enabled since Chrome 48-49 (see  issue 662901 ):

4.5 sec in Chrome 53 for big.txt from a local ramdrive
1.5 sec in Chrome 53 with "--disable-blink-features=AlwaysUseComplexText" command line

This command line doesn't work anymore in Chrome 54+ because the ability to disable the feature was removed.

Comment 4 by pmeenan@chromium.org, Dec 28 2016

Components: -Blink>Loader Blink>Fonts
Status: Untriaged (was: Unconfirmed)
The resource loading itself doesn't appear to be an issue but the complexity of displaying the content is.  It isn't a UI issue in the terms of Chrome's shell but it is a rendering issue.  Tagging it for the Font team to take a look at.

Comment 5 by e...@chromium.org, Jan 2 2017

Mergedinto: 677839
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment