Darin Fisher wrote: > I suspect this is at least one of the bigger issues. > I also suspect that process creation is a problem on Windows. We should > probably look into having a spare child process on Windows to minimize new > tab jank. Maybe there is a bug on this already?
This shouldn't be restricted to Windows, we should do it on all platforms. And we should start the first one as early as possible during the startup process. When I benchmarked this a few months ago on a fairly ordinary Mac, it took nearly 100ms from the time that the browser started a renderer to the time that the renderer was ready to service requests. A decent chunk of that is load time and pre-main initialization in system libraries. It's beyond our control, but there's no reason we can't make it happen sooner. Mark --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
