On Oct 28, 2009, at 11:29 AM, Mark Mentovai wrote:
> You could use this argument to shoot down keeping a spare warmed-up > renderer ready to go at other times, but I don't think it's relevant > to the startup case. We weren't just talking about startup — f'rinstance, Darin mentioned "new-tab jank". > I suspect that most (but not all) of the stuff that the renderer needs > to read to warm itself up will already be in the buffer cache. Not on a cold launch, since the renderer uses a lot of code (like WebCore) that the browser doesn't, and will be paging that stuff in. We'll need to benchmark both scenarios. —Jens --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
