You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not the case that the profiled code uses >1 CPU seconds. It spends the entire time sleeping. The default timer for cProfile is a wallclock timer. The output should reflect this.
On Tue, Nov 09, 2010 at 07:15:57PM +0000, Jean-Paul Calderone wrote:
> >>> cProfile.run("import time; time.sleep(1)")
> 4 function calls in 1.012 CPU seconds
>
> It is not the case that the profiled code uses >1 CPU seconds. It
> spends the entire time sleeping. The default timer for cProfile is
> a wallclock timer. The output should reflect this.
So, It should just be 1.012 seconds, instead of 1.012 CPU seconds. Correct?
Or is there any other technically more accurate way to say?
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: