|
|
Why writing a profiler tester? Does that make sense at all?
Every
profiler tries to deliver accurate results. With the profiler
tester you can find out, if a profiler can handle the basic problems:
Another reason for the existence of this tester is, that different principles of profiling exist:
A
program waits in a loop where ProcessMessage is called due to waiting
for
an external event. Certainly nobody wants to know, how long the program
waits. As a consequence the cyles processed while waiting should not be
counted. Other events which are processed while waiting have to be
counted,
but not as child times of the waiting procedure. Some profilers do not
have this feature.
Last page update:
7/25/2010