Updates:
Status: Started
Owner: [email protected]
Cc: tony.chromium [email protected]
Labels: -Pri-3 Pri-2
Comment #10 on issue 6844 by [email protected]: Consider starting renderer
processes from a background thread
http://code.google.com/p/chromium/issues/detail?id=6844
We started getting data back from the histograms that Brett added. The
numbers
surprised me a bit, especially on Linux!
from http://chromedashboard.mtv.corp.google.com/#view=histograms, Windows
has a mean
time of 119ms for first process creation, and 49ms afterwards. Linux,
http://www.corp.google.com/~chrome-eng/dashboards/histograms/?
data_source=last_7_days.js&version=4.0.223.5-L&group=MPArch&histogram=MPArch,
has
1174 and 3! I don't understand how the first numbers are so slow.
I think these numbers are worse when considering session restore bringing
up 10 tabs
etc. This means on Windows we can be stuck for half a second in total.
Seems worth
doing asynchronously.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
