bpo-34060: Report system load when running test suite for Windows#8287
bpo-34060: Report system load when running test suite for Windows#8287ammaraskar wants to merge 2 commits into
Conversation
|
A quick note on the LOADAVG_FACTOR_1F and SAMPLING_INTERVAL; that given dampening factor is for a sample rate of 5 seconds. SAMPLING_INTERVAL should really be changed to 5 or re-run the equation with the different interval. |
Sorry, something went wrong.
|
Thanks again Jeremy, I changed the interval to 5 to be more in line with the Linux scheduler. |
Sorry, something went wrong.
|
Also, I don't think this actually needs a NEWS entry right? It relates to cpython build process and doesn't actually affect the language. Could you mark it with the |
Sorry, something went wrong.
|
What extra runtime dependencies does this add to
(Haven't looked too closely at the implementation yet, but when I do, it will be with the view that it is a public API change. Unless you rework it into its own module first.) |
Sorry, something went wrong.
|
(Edited above post). Let me take that back - was thinking of |
Sorry, something went wrong.
|
Aah yeah I think you have a good point, I think making it its own module would be a bit overkilll so I'll clean up the API anticipating some public usage. |
Sorry, something went wrong.
Sorry, something went wrong.
See the bpo ticket for more technical details on the implementation and otherwise.
https://bugs.python.org/issue34060