On Tue, Oct 27, 2009 at 8:26 AM, Antony Sargent <[email protected]> wrote: > Page Cycler Tests > Since the page cycler tests take a long time to run, we've only added one > extensions case to 2 of the individual data sets: Moz (relatively simple > pages, less javascript) and MoreJS (more complicated DOM and javascript). > The Moz set runs very quickly, typically something like 40ms per page on a > fast machine. The MoreJS set runs much more slowly, typically something like > 190-200ms per page on a fast machine. We use the "_extcs1" suffix on the > test names to denote "extensions with 1 content script". > Time > Moz: 10-17% increase in cycle time (absolute increase of ~4-5ms per page) > MoreJS: 2-4% (absolute increase of ~5-10ms per page, perhaps a little higher > than Moz due to v8 having more garbage to collect?)
FYI, we got the Moz one down to about .7% regression. See here: http://build.chromium.org/buildbot/perf/xp-release-dual-core/moz/report.html?history=150 This was done by delaying injection until after page load is complete for fast pages. The heuristic is that we inject at min(DOMContentLoaded + 200ms, onload). The idea is to not delay fast pages, but not to have to wait too long for injection for slow pages. We still have work to do on Chrome startup, but I'm hopeful we can fix that, too. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
