gecko-dev/tools/performance/layout
2000-06-23 00:18:09 +00:00
..
tables New Daily Performance file. Not part of build. 2000-03-24 21:42:41 +00:00
40-url-dup.txt Each URL is duplicated so the second time all images and the page itself will be from cache: catches the rogue image that is not on the file system, and it also limits the effect of the file system in skewing the numbers. Not part of build 2000-04-14 23:12:20 +00:00
40-url.txt update the path in the file URLs. NOT PART OF BUILD 2000-02-23 17:06:38 +00:00
Averagetable2.pl Additional BuildID parsing needed by Bindu. Not part of build. 2000-06-23 00:18:09 +00:00
collect.pl New script for down-and-dirty collection of performance data (author:waterson). 2000-06-02 00:53:52 +00:00
Footer.pl Updated for new location of the chrome files used in extraction of the BuildID. Not part of build. 2000-05-31 20:33:22 +00:00
genfromlogs.pl Updated scripts to deal with the changes to the Viewer output and changes to the BuildID file location and format 2000-05-11 21:15:43 +00:00
Header.pl Updated for new location of the chrome files used in extraction of the BuildID. Not part of build. 2000-05-31 20:33:22 +00:00
history.pl
history.txt Daily run added for 6-20. Not part of build 2000-06-22 22:03:24 +00:00
perf-doc.html Adding documentation on the Perf tool. Not part of build. 2000-03-17 20:07:57 +00:00
perf.pl Updated scripts to deal with the changes to the Viewer output and changes to the BuildID file location and format 2000-05-11 21:15:43 +00:00
property.inc QA Partner script: deprecated but sometimes it is required, like when viewer's -f option is broken. 2000-02-25 20:29:45 +00:00
property.t QA Partner script: deprecated but sometimes it is required, like when viewer's -f option is broken. 2000-02-25 20:29:45 +00:00
readme.txt Updated to include the websites install. 2000-02-23 18:11:40 +00:00
uncombine.pl Updated scripts to deal with the changes to the Viewer output and changes to the BuildID file location and format 2000-05-11 21:15:43 +00:00

readme.txt - if there is a perf.html file, read that, it contains the full documentation. This file is a stop-gap until the documentation is completed.

The cached websites must be downloaded and installed under the
performance\layout directory. You can find them at
http://techno/users/attinasi/publish and click on the WebSites in ZIP format.
Unzip the archive and make sure the websites extracted correctly.

BASICS: to run the performance tool simply execute the perf.pl script.
 eg. perl perf.pl Daily-021400 s:\mozilla\dist\win32_o.obj CPU

This command will run viewer, crawl the top 40 URLs, dump the results to a file and subsequently parse the file to create the HTML performance table.

To run Mozilla instead of viewer, edit the perf.pl script and change the $UseViewer variable value to 0. Then, run the perf.pl script, except there is an additional argument:
 perl perf.pl Daily-021400 s:\mozilla\dist\win32_o.obj CPU profilename

Including the profilename is essential, and the profilename specified must reference a valid profile.

The output from the scripts is:

1) BUILD_NAME.html in the Tables directory - the performance table
2) BUILD_NAME-TrendTable.html in the Tables directory - the trending table
3) BUILD_NAME directory under Logs - includes all of the original log files
4) history.txt - appends the latest averages to the history file

If a run is aborted or is not to be used, the history.txt file must be edited to remove the bogus run.

If problems arise in the scripts, there are debug routeins in each script file. Simply remove the comment from the print line and re-run to get diagnostics dumped to the console.



... more to come...