Performance:Tinderbox Tests: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add Tr/Tgfx/Tsvg)
(Replaced content with "Please reference https://wiki.mozilla.org/Buildbot/Talos Buildbot/Talos instead.")
 
(14 intermediate revisions by 10 users not shown)
Line 1: Line 1:
Original document imported from http://www.mozilla.org/performance/tinderbox-tests.html and original author is Chris McAfee <mcafee@netscape.com>.
Please reference [[https://wiki.mozilla.org/Buildbot/Talos Buildbot/Talos]] instead.
 
= Notes before starting =
 
*  When running these tests on your local machine, be sure to turn off extra stuff to reduce noise in your results. This means, irc, browsers, aim, httpd, things like that.
* Test with an optimized build. --enable-optimize, --disable-debug
* Running X & twm will reduce gnome noise.
* Install the Time::HiRes perl module for better timer resolution (see <code>mozilla/tools/performance/startup/gettime.pl</code>).
* Set this pref for stdout test output: user_pref("browser.dom.window.dump.enabled", true);
* In the commands below, <code>&lt;appname&gt;</code> is <code>firefox</code> or <code>seamonkey</code> or <code>mozilla</code> or whatever you're testing.
 
= Ts: Startup time =
 
This test passes in begin time as a cgi argument, and JS onload handler in startup-test.html computes the end time.
 
    cvs co mozilla/tools/performance/startup
    startup-unix.pl <path>/dist/bin/&lt;appname&gt;
 
= Txul: XUL window open time =
 
10 windows are opened/closed and median and average times are printed.
 
    &lt;appname&gt; -chrome "file://<path>/mozilla/xpfe/test/winopen.xul"
 
= Tp: Pageloader time =
 
jrgm's pageload test. You need to set up a server to run this. [How does one do that??] Point your browser at this server and it crunches for up to 15-20 min depending on your machine speed, and produces a graph and average time value.
 
If you have a slow machine (e.g. < 300MHz) you may need to increase the timeout value from 15000 to say 30000.
 
= Tdhtml: DHTML performance =
 
This test runs a number of DHTML testcases several times, then prints out median and average times for each testcase, as well as the raw data, and the geometric mean of the median times. To run, just load the [http://www.mozilla.org/performance/test-cases/dhtml/runTests.html test driver].
 
= Classic (refcnt) Bl/Lk: Bloat & Leak numbers =
 
For a non-debug build, add this to your <code>.mozconfig</code>:
 
  ac_add_options --enable-logrefcnt
 
and reconfigure and rebuild. Then run the app on the bloaturls list of urls:
 
  &lt;appname&gt; resource:///res/bloatcycle.html
 
Bloat and leak summaries dumped out to <code>stdout</code>.
If you want to compare two runs (e.g. test a change) do something like this:
 
  cvs co mozilla/tools/tinderbox/bloatdiff.pl
  &lt;appname&gt; resource:///res/bloatcycle.html > a.out
    **make change**
  &lt;appname&gt; resource:///res/bloatcycle.html > b.out
  bloatdiff.pl a.out b.out
 
= Trace-Malloc Bl/Lk: Bloat & Leak numbers =
 
Add this to your <code>.mozconfig</code>:
 
  mk_add_options MOZ_CO_MODULE="mozilla/tools/trace-malloc"
  ac_add_options --enable-trace-malloc
 
Then do:
 
  cvs co mozilla/tools/trace-malloc
 
and rebuild.  Then run the app on the bloaturls list of urls:
 
  &lt;appname&gt; resource:///res/bloatcycle.html
 
Bloat and leak summaries dumped out to <code>stdout</code>. More info about both bloat tests [http://www.mozilla.org/performance/leak-brownbag.html#tbox in the leak brownbag].
 
= Tr/Tgfx/Tsvg: Rendering Performance numbers =
 
These numbers measure raw rendering speed, without network or layout overhead.  See [[Mozilla2:Trender]] for more information.

Latest revision as of 16:48, 18 May 2012

Please reference [Buildbot/Talos] instead.