tools/performance/layout/readme.txt

Wed, 31 Dec 2014 06:09:35 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Wed, 31 Dec 2014 06:09:35 +0100
changeset 0
6474c204b198
permissions
-rw-r--r--

Cloned upstream origin tor-browser at tor-browser-31.3.0esr-4.5-1-build1
revision ID fc1c9ff7c1b2defdbc039f12214767608f46423f for hacking purpose.

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

mercurial