Thanks for pointing me to your analysis. Now I know it wasn't me doing something wrong.

hotspot did lead me to knock down a major performance bottleneck one time. I found that zipfile.ZipFile() basically read the entire zip file in instantiation time, even though you may only need one file from it subsequencely.

In anycase the number of function call seems to make sense and it should give some insight to the runtime behaviour. The CPU time is just so misleading.



aurora wrote:

But the numbers look skeptical. Hotspot claim 71.166 CPU seconds but the actual elapsed time is only 54s. When measuring elapsed time instead of CPU time the performance gain is only 13% with the profiler running and down to 10% when not using the profiler.
Is there something I misunderstood in reading the numbers?

Well, I'm confused too. Look at my post from a few months ago: http://tinyurl.com/6awzj (note that my code contained a few errors and that you need to use the fixed code that I posted a few replies later).

Perhaps somebody can explain a bit more about this this time? :-)

At the moment, frankly, hotspot seems rather useless.

--Irmen

-- http://mail.python.org/mailman/listinfo/python-list

Reply via email to