The Tor Browser / file comparison
comparison: tools/performance/layout/readme.txt
tools/performance/layout/readme.txt
- branch
- TOR_BUG_9701
- changeset 3
- 141e0f1194b1
equal
deleted
inserted
replaced
| -1:000000000000 | 0:038bde890d34 |
|---|---|
| 1 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. | |
| 2 | |
| 3 The cached websites must be downloaded and installed under the | |
| 4 performance\layout directory. You can find them at | |
| 5 http://techno/users/attinasi/publish and click on the WebSites in ZIP format. | |
| 6 Unzip the archive and make sure the websites extracted correctly. | |
| 7 | |
| 8 BASICS: to run the performance tool simply execute the perf.pl script. | |
| 9 eg. perl perf.pl Daily-021400 s:\mozilla\dist\win32_o.obj CPU | |
| 10 | |
| 11 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. | |
| 12 | |
| 13 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: | |
| 14 perl perf.pl Daily-021400 s:\mozilla\dist\win32_o.obj CPU profilename | |
| 15 | |
| 16 Including the profilename is essential, and the profilename specified must reference a valid profile. | |
| 17 | |
| 18 The output from the scripts is: | |
| 19 | |
| 20 1) BUILD_NAME.html in the Tables directory - the performance table | |
| 21 2) BUILD_NAME-TrendTable.html in the Tables directory - the trending table | |
| 22 3) BUILD_NAME directory under Logs - includes all of the original log files | |
| 23 4) history.txt - appends the latest averages to the history file | |
| 24 | |
| 25 If a run is aborted or is not to be used, the history.txt file must be edited to remove the bogus run. | |
| 26 | |
| 27 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. | |
| 28 | |
| 29 | |
| 30 | |
| 31 ... more to come... | |
| 32 |
