Comment #12 on issue 6844 by [email protected]: Consider starting renderer processes from a background thread http://code.google.com/p/chromium/issues/detail?id=6844
What I see is a bimodal distribution. Many people start in 50ms, but a second group take much longer (nearly a second). I can hypothesise that people starting from a cold disk cache are in the second group. Starting the renderer is the first time that we hit WebKit code and pulling code pages from the disk takes a while. People in the first group are starting with a warm disk cache and don't have this issue. -- 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 -~----------~----~----~----~------~----~------~--~---
