CPU regression in github actions since March 17th #190177
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Bug
What GitHub Actions topic or product is this about?
General
Discussion Details
We are seeing unusual behavior on our Github Actions performance with the standard free tier 4 core amd64 linux tests. We have CPU-heavy compile jobs that started taking >2x longer sometime between
Tue, 17 Mar 2026 00:12:56 GMTandTue, 17 Mar 2026 01:11:11 GMT. These jobs used to consistently take 3min and now consistently take 6m40s before/after this date. This is not related to a code change on our end, as we did not have any code change and we have re-run older code and seen the slow behavior.Has anyone else seem similar issues in actions performance?
Beta Was this translation helpful? Give feedback.
All reactions