New issue
Advanced search Search tips

Issue 842069 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Take more time when decoding text resource since r358275

Project Member Reported by gyuyoung...@lge.com, May 11 2018

Issue description

r358275 had changed the decoding way of the text resource with the progressive decoding in order to avoid merging SharedBuffer segments. However, it looks like that the process time of text decoding was increased. Especially, it increased the launching time when a web app is launched on web runtime based on Chromium.

According to my simple test, r358275 increased about 28ms the processing time in TextResource::DecodedText when loading nytimes.com.

 - With original implementation: 41ms
 - Current implementation: 69ms

- Test scenario.
  1. Download https://www.nytimes.com to local system.
  2. Add a time measure code inside TextResource::DecodedText
  3. Launch Chrome with the downloaded nytimes.com files.
   e.g) ./out/Debug/chrome ~/Nytimes.html


 
Project Member

Comment 1 by sheriffbot@chromium.org, May 11 2018

Labels: Hotlist-Recharge-BouncingOwner
Owner: ----
The assigned owner "gyuyoung.kim@lge.com" is not able to receive e-mails, please re-triage.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: kouhei@chromium.org
Components: Blink>Loader

Comment 3 by gyuyoung...@lge.com, May 12 2018

Owner: gyuyoung...@lge.com

Comment 4 by gyuyoung...@lge.com, May 12 2018

Owner: gyuyoung...@chromium.org

Comment 5 by gyuyoung...@lge.com, May 14 2018

Status: WontFix (was: Untriaged)
The current implementation was a little bit faster than the original one in release build. So I would like to re-open when I have more clear evidence. Close for now.

Sign in to add a comment