Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Temporary documentation...

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@61494 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
attinasi%netscape.com
2000-02-23 18:07:46 +00:00
parent f58d902e54
commit ff72396027
1 changed files with 27 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
mozilla/tools/performance/layout/readme.txt Normal file
View File

@@ -0,0 +1,27 @@
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.
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...