➜

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 pitrou
Recipients georg.brandl, neologix, pitrou
Date 2011-11-26.11:00:36
SpamBayes Score 0.00014046542
Marked as misclassified No
Message-id <1322304937.3400.1.camel@localhost.localdomain>
In-reply-to <1322304961.75.0.728095247439.issue13481@psf.upfronthosting.co.za>
Content 
> With CLOCK_PROCESS_CPUTIME_ID:
> - depending on the platform, we'll measure either wall-clock time or
> CPU time

Indeed. I thought CPU time would be more useful (and that's the point of
the patch) but perhaps it breaks the spec.

> - preemtion, blocking syscalls, etc won't be accounted for (so, for
> example, I/O-related tests will be meaningless)

But does it include kernel CPU time for the given process?
History
Date User Action Args
2011-11-26 11:00:37pitrousetrecipients: + pitrou, georg.brandl, neologix
2011-11-26 11:00:36pitroulinkissue13481 messages
2011-11-26 11:00:36pitroucreate