Essentially this. Some of the page cyclers have fairly interesting data
sets.
I think we are fairly lacking in good real-world performance tests to do
comparisons like this, which is kind of unfortunate. I'd love to be able to
point a build with a speculative patch in it at the internet and then have
it report back how well it did but there are a lot of variables to control.
- James
On Tue, Nov 3, 2009 at 10:38 AM, Anton Muhin <ant...@chromium.org> wrote:
> Thanks a lot, Peter.
>
> Yes, I am aware of those. Just wanted to run something before committing
> :)
>
> I actually ran some DOM related tests. Adam (on IM) suggested to run
> SunSpider, V8 and page load cyclers. I am going to do it and if
> numbers are fine, then would try to commit my change.
>
> yours,
> anton.
>
> On Tue, Nov 3, 2009 at 9:25 PM, Peter Kasting <pkast...@google.com> wrote:
> > On Tue, Nov 3, 2009 at 7:30 AM, Anton Muhin <ant...@chromium.org> wrote:
> >>
> >> So the question: how could I check that I won't (notably) regress
> >> Chromium performance with this change?
> >
> > We have perf bots; you can check in and look at the effects there, and
> there
> > might even be a way to get perf results from the tryservers.
> > PK
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
