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

Issue 832642 link

Starred by 2 users
Status: Assigned
Owner:
█ hpayer@chromium.org
Last visit > 30 days ago
Cc:
leszeks@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome extensions aren't cached by V8

Project Member Reported by leszeks@chromium.org, Apr 13 2018 
V8 code caching isn't used for chrome extensions, which means that they have to be compiled more than necessary. Currently, extension compiles fall into the "other" bucket of script compilation statistics, and that takes up a solid ~40% of total script compilation time on Windows -- most of which I believe is extensions.
compile_time_windows_inline.png
95.5 KB View Download

Comment 1 by lazyboy@chromium.org, Apr 13 2018

Status: Assigned (was: Untriaged)
Untriaged w/ owner -> Assigned

Comment 2 by rdevlin....@chromium.org, Apr 13 2018 

Untriaged with owner -> assigned

Comment 3 by hpayer@chromium.org, Apr 17 2018

Owner: leszeks@chromium.org

Comment 4 by hpayer@chromium.org, Apr 17 2018

Cc: leszeks@chromium.org
Owner: hpayer@chromium.org
►

Sign in to add a comment