Performance:Tinderbox Tests: Difference between revisions

Jump to navigation Jump to search
Line 23: Line 23:
     &lt;appname&gt; -chrome "file://<path>/mozilla/xpfe/test/winopen.xul"
     &lt;appname&gt; -chrome "file://<path>/mozilla/xpfe/test/winopen.xul"


= Tp: Pageloader time =
= Tp, Tp2 and the Pageloader extension: Page load 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.
jrgm's pageload test. You need to set up a server to run this. The source code is at http://lxr.mozilla.org/mozilla/source/tools/page-loader/ but note that it relies on some outdated Perl modules. 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.
If you have a slow machine (e.g. < 300MHz) you may need to increase the timeout value from 15000 to say 30000.
Alternatively, use darin's standalone Tp2 test:
http://lxr.mozilla.org/mozilla/source/tools/performance/pageload/
Or rhelmer's pageloader extension:
http://lxr.mozilla.org/mozilla/source/testing/tools/pageloader/
Tp2 runs inside the content area of the browser, while the pageloader extension runs without browser chrome. They are based on the same (Javascript) code, and both produce numbers suitable for reporting to Tinderbox or the graph server.
It is recommended that you save all of the sites you wish to test to a local webserver, so that the network and remote webservers don't introduce unwanted variance.


= Tdhtml: DHTML performance =
= Tdhtml: DHTML performance =
canmove, Confirmed users
1,511

edits

Navigation menu