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
pyinstrument only records one thread at a time. However, due to the GIL, the performance of one thread could be affected by a different active thread in the same program.
This could be compared with the program CPU time - if the current thread is less than 80% of the program's CPU time, it's likely that that other thread was slowing the profiled one down - this should be communicated in pyinstrument's output.
It would be even better if we could track the time spent inside the GIL (and even subtract it), but I'm not sure how to do that!
The text was updated successfully, but these errors were encountered:
pyinstrument only records one thread at a time. However, due to the GIL, the performance of one thread could be affected by a different active thread in the same program.
Python can now give CPU time per-thread:
This could be compared with the program CPU time - if the current thread is less than 80% of the program's CPU time, it's likely that that other thread was slowing the profiled one down - this should be communicated in pyinstrument's output.
It would be even better if we could track the time spent inside the GIL (and even subtract it), but I'm not sure how to do that!
The text was updated successfully, but these errors were encountered: