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
We should create a simple utility that tracks resource usage (CPU, memory, disk, etc...) and uploads a graph of the usage over time over the course of the CI run. Even cooler would be if we can distill it down to a self-contained HTML page with interactive plots a la Plotly.js or similar, but I'll take static .png's at first if that's easiest.
The rationale behind this being that we should get definitive proof of our resource usage over time and make it trivially easy for any contributor to inspect for themselves whether a PR failed due to memory exhaustion, disk space exhaustion, etc...
This will be most useful for dedicated VM machines (such as the windows KVM runners) but would also be useful (albeit perhaps less clear) for shared environments. If this plays well with cgroups, we can at least get semi-clear CPU usage charts, if not memory usage charts (as we don't segregate memory usage.... yet)
The text was updated successfully, but these errors were encountered:
It's a self-contained rust executable that reads system statistics (CPU usage, memory usage, disk usage, etc...) and writes out a .csv file of those values over time until the process is killed. It's not in a completely usable state yet, (still some bugs) but it's getting there. The TODO list from here on out is:
Fix Windows disk path resolution bug (Paths need to be properly resolved according to the \\?\C:\... scheme)
Maybe add some simple self-tests?
Spin up a Julia process, consume some resources and verify that they show up properly?
We should create a simple utility that tracks resource usage (CPU, memory, disk, etc...) and uploads a graph of the usage over time over the course of the CI run. Even cooler would be if we can distill it down to a self-contained HTML page with interactive plots a la Plotly.js or similar, but I'll take static
.png
's at first if that's easiest.The rationale behind this being that we should get definitive proof of our resource usage over time and make it trivially easy for any contributor to inspect for themselves whether a PR failed due to memory exhaustion, disk space exhaustion, etc...
This will be most useful for dedicated VM machines (such as the windows KVM runners) but would also be useful (albeit perhaps less clear) for shared environments. If this plays well with cgroups, we can at least get semi-clear CPU usage charts, if not memory usage charts (as we don't segregate memory usage.... yet)
The text was updated successfully, but these errors were encountered: