well, now that I actually look at those revisions instead of just the descriptions, it doesn't seem to me like they could be to blame. I'll investigate this tomorrow with the perf try server.
-- Evan Stade On Wed, Sep 2, 2009 at 7:31 PM, Evan Stade<[email protected]> wrote: >>> Maybe r25099? I don't know how long it takes between commit time and >>> when the results show up in the graph, so this is a rough guess. > > the perf tests are run continuously on the buildbot, so the regression > is somewhere in the range between 25120 and 25132.My suspicion lies on > r25126 or 25128. > >>> >>> r25099 -- >>> Plumb request interception into the appcache library for both chrome >>> and test_shell. >>> ... >>> Chrome: >>> * Each UserProfile instantiates a ChromeAppCacheService, which is >>> derived from an appcache library class. >>> >>> >>> On Wed, Sep 2, 2009 at 6:21 PM, Evan Martin<[email protected]> wrote: >>> > >>> > >>> > http://build.chromium.org/buildbot/perf/linux-release-hardy/startup/report.html?history=150 >>> > >>> > We seem to have lost about 50% around r25132, but the commits around >>> > there aren't at all suspicious. :( >>> > Any guesses? Maybe Brett's change? >>> > >>> > > >>> > >>> >>> >> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
