WebKit.Profiler | index /usr/local/share/webware/WebKit/Profiler.py

`Profiler.py
Stores some values related to performance.
These are usually set by Launch.py or AppServer.py.
To get profiling going, locate the "runProfile = False" line towards the top
of WebKit/Launch.py and change the "False" to "True", or start the Launch.py
script with the --run-profile option. When the app server shuts down it
will write a profiling report "profile.pstats" in the directory containing
the Launch.py script which can be quickly examined from the command line:
$ cd Webware
$ bin/printprof.py WebKit/profile.pstats
Using the RunSnakeRun (http://www.vrplumber.com/programming/runsnakerun/)
GUI utility you can even visualize the data in the profile.pstats file.
You might also wish to dump the profiling stats on demand (as in, by
clicking or reloading a URL for that purpose). Read further for details.
The variables in this module are:
profiler
An instance of Python's profile.Profiler, but only if Launch.py is
started with profiling enabled. Otherwise, this is None.
You could access this from a servlet in order to dump stats:
from WebKit.Profiler import dumpStats
dumpStats()
With some work, you could dump them directly to the page in a
readable format.
startTime
The earliest recordable time() when the app server program was
launched.
readyTime
readyDuration
The time() and duration from startTime for when the app server
was ready to start accepting requests. A smaller readyDuration
makes application reloading faster which is useful when
developing with AutoReload on.`

Functions
`` |  | dumpStats(file='profile.pstats') reset() `Invoked by DebugAppServer in support of AutoReload.` runCall(func, *args, **kwargs)

Data
`` |  | profiler = None readyDuration = None readyTime = None startTime = None statsFilename = 'profile.pstats'