This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author alexandre.vassalotti
Recipients alexandre.vassalotti, barry, benjamin.peterson, brett.cannon
Date 2008-10-06.22:06:06
SpamBayes Score 2.6246102e-08
Marked as misclassified No
Message-id <1223330767.54.0.0824763469201.issue2744@psf.upfronthosting.co.za>
In-reply-to
Content
Have you verified the numbers? They don't look right to me.

The problem is the 2nd argument of cProfile's constructor has a
different semantic meaning than the one for profile.py. For profile.py,
it is used to set the "bias" (I presume it means the overhead) of the
profiler. But for cProfile, it's the unit (in seconds?) of timer used.

Personally, I have no idea which semantic should be preferred. So
perhaps, the best thing to do for now is remove the second argument from
the cls.profilerclass() call in test_profile.ProfileTest:

class ProfileTest:
    ...
    def do_profiling(cls):
        ...
        prof = cls.profilerclass(timer, 0.001)
        ...
History
Date User Action Args
2008-10-06 22:06:07alexandre.vassalottisetrecipients: + alexandre.vassalotti, barry, brett.cannon, benjamin.peterson
2008-10-06 22:06:07alexandre.vassalottisetmessageid: <1223330767.54.0.0824763469201.issue2744@psf.upfronthosting.co.za>
2008-10-06 22:06:07alexandre.vassalottilinkissue2744 messages
2008-10-06 22:06:06alexandre.vassalotticreate