Show CPU and Memory utilization for Jobs

[anarazel]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Metrics & Insights

Discussion Details

When trying to improve the performance of CI runs it is rather important to know whether the bottleneck is too high resource utilization (CPU, Memory) or inability to use the resources (e.g. not enough build/test concurrency, being latency bound, ...).

Measuring those resources is possible today, but it's complicated, platform dependent and the output cannot easily be shown in a immediately understandable way (like graphs in the per-job view and in the already existing usage / performance metric views, so one can see things like whether CPU utilization has increased over time).

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Payal-goell]

This is valuable feedback. Understanding whether CI slowdowns come from resource saturation (high CPU/memory usage) or workflow inefficiencies (poor parallelism, I/O waits, network latency) is essential for optimizing pipeline performance.
Adding built-in resource utilization metrics and visual dashboards—such as CPU, memory, disk I/O, and concurrency graphs at both the per-job and historical usage level—would make bottlenecks much easier to identify. This would help users quickly determine whether they need to scale resources or optimize job configuration, ultimately improving CI efficiency and reducing troubleshooting complexity.

[maheerCodes]

big +1 on this ,,,agree with everything Payal said. native per-job resource graphs would save a ton of guesswork
in the meantime ,,,a workaround thats worked decently for me on node /js projects specifically :

• add a simple background logging step at the start of your job that polls system resources every few seconds and writes to a file ,,,then upload that as an artifact at the end.something like :

( while true; do echo "$(date +%s) $(free -m | awk 'https://github.com/Mem/{print $3}') $(cat /proc/loadavg)"; sleep 5; done & echo $! > monitor.pid )

then kill it at the end of the job and upload monitor.log as an artifact. crude but gives you a timeline you can plot afterward

• for node specifically,,,/usr/bin/time -v npm test(on linux runners)gives you peak memory and cpu time for that single step without neeeding continuous polling,,much simpler if you just want a summary rather than a timeline,
• theres also a marketplace action called actions/runner-images insights or third party ones like mxschmitt/action-tmate style monitors people have hacked together for this exact gap ,,, worth searching the marketplace for "resource monitor" action ,a few exist as stopgaps.

none of these give you the clean integrated graph experience this discussion is asking for though,,,,,,just a way to get some visibility while waiting on a native feature 🩷🩷🩷🩷