Re: [Pyunit-interest] Timing

[Steve P. <ste...@ya...>]

Michal Wallace wrote:
> On Fri, 6 Apr 2001, Steve Purcell wrote:
> > Yes, as Michal notes, using the profiler is the easiest option,
> > though it will cause the tested code to run significantly slower.
> 
> Have you actually tried this? The profiler is usually blazingly fast
> has almost no overhead whatsoever (there's hooks for it directly in
> the VM). I run it as part of my cgi wrapper when I'm developing, and
> it's quite comfortable.  Even if you had a ton of test cases, I would
> think it should take a half a second or so at the worst.


I based my comment on some experiences I had with coverage measurement; there,
the callback overhead is much higher because a callback is made for each
executed line, rather than for each function, as is the case when profiling.

So on reflection, "significantly slower" is probably significantly
overstated. :-)

-Steve

-- 
Steve Purcell, Pythangelist
Get testing at http://pyunit.sourceforge.net/
Any opinions expressed herein are my own and not necessarily those of Yahoo