diff options
| author | jam <jam@chromium.org> | 2016-03-22 22:34:24 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-03-23 05:35:38 +0000 |
| commit | 75c4422d8fdabd231f40a6c9235f4512f0170268 (patch) | |
| tree | 95d8a4b3b54dc0ff1e22ad25e0fefcc7afb7d832 /content/public/browser/devtools_manager_delegate.h | |
| parent | b746ad977e2ad04e17a0792bd313f6e9d7a4be74 (diff) | |
| download | chromium_src-75c4422d8fdabd231f40a6c9235f4512f0170268.zip chromium_src-75c4422d8fdabd231f40a6c9235f4512f0170268.tar.gz chromium_src-75c4422d8fdabd231f40a6c9235f4512f0170268.tar.bz2 | |
Remove logic for lazy initialization of WebKit.
See "Extensions impact on startup?" thread on (internal) chrome-fast mailing list from 8/14/2015 for background, which showed that effectively undoing this logic showed a 3% reduction on first_non_empty_paint_time. This lazy initialization used to be a performance win when it was added years ago, but has since become a performance drag. Since it's effectively not used now (since ChromeContentRendererClient::RenderThreadStarted always initializes WebKit through its call to RenderThread::RegisterExtension), just remove this unused logic.
Review URL: https://codereview.chromium.org/1821413003
Cr-Commit-Position: refs/heads/master@{#382795}
Diffstat (limited to 'content/public/browser/devtools_manager_delegate.h')
0 files changed, 0 insertions, 0 deletions