I'm interested in tests that mutates or reads the DOM but does not paint or render. So no layout or GFX is involved in the timing, unlike our Tdhtml tests which test a mix of things. Having these issues isolated would help us catch regressions and understand performance issues. Three specific tests which can be adapted immediately: https://bugzilla.mozilla.org/attachment.cgi?id=291255 for Bug 375225 is an https://bugzilla.mozilla.org/attachment.cgi?id=288941 http://nontroppo.org/timer/Hixie_DOM.html But we can add more as we find them.
Some more: http://extjs.com/playpen/slickspeed/ http://andrewdupont.net/test/double-dollar/ http://www.jackslocum.com/blog/2006/10/06/domhelper-create-elements-using-dom-html-fragments-or-templates/ http://www.jackslocum.com/blog/2007/01/12/domquery-in-response-to-jquerys-response/ JResig where are JQuery's speed tests?
We need to be very careful with things like the slickspeed test... It's very easy with tests like that to measure the wrong thing (e.g. to allow frame dropping).
This just got posted with some interesting comparisons: http://www.coachwei.com/blog/_archives/2008/1/22/3480119.html
Can we get a side-by-side on that last test with 1.8 and 1.9?
(In reply to comment #4) > Can we get a side-by-side on that last test with 1.8 and 1.9? > http://spreadsheets.google.com/ccc?key=pq20lsXjZGAx1d9Mwc5s8KQ&hl=en
Nice... Except for that array sorting thing, we win. ;)
Came up in triage - anything left to do here?
The tests mentioned in the first few comments need to be converted into tests that talos understands so that they can be automated - it would also be nice to shake out any other tests that look like they should go under this umbrella.
Component: Testing → Release Engineering: Projects
Priority: -- → P3
Product: Core → mozilla.org
Version: unspecified → other
I have some DOM tests online now: http://v2.dromaeo.com/?dom It doesn't seem like it would be that bad to hook this in to the existing infrastructure, will need to investigate more.
For comparison you can see how the dromaeo/tjss test was integrated into talos here: /mozilla/testing/performace/talos/page_load_test/jss That contains the individual pages to be tested along with a manifest file. The pages have been set up to run onLoad and then drop timing information to the pageloader extension.
There's a lot of different test suites referenced here. Let's open a new bug for a specific set of DOM tests to integrate as Tdom.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
I was under the impression that this bug was about deciding what that set should be....
The determination of what tests are useful and valid should not be a bug filed against Release Eng - we automate the tests that are provided for us (for the most part). That sounds like something to be filed against firefox itself somewhere.
This bug wasn't filed against Rel Eng initially. You moved it there... If it's in the wrong place, please move it to the right one instead of wontfixing?
Moving closed Future bugs into Release Engineering in preparation for removing the Future component.
Component: Release Engineering: Future → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.