Skip to content
Discussion options

You must be logged in to vote

Hi @blackliner ,

I’d like to suggest enhancing the actions.runner.service.template file to support optional configuration of CPUQuota and MemoryMax. This would provide a flexible and native way to control system resource limits for each GitHub Actions runner instance when using systemd.


Use case

In scenarios where multiple runners are hosted on a single, powerful machine (e.g., self-hosted runners for parallel jobs), it’s important to contain their resource usage. Being able to configure these systemd directives directly would help:

[Service]
CPUQuota=25%
MemoryMax=2G

This would ensure each runner doesn’t exceed a defined CPU or memory usage threshold, avoiding contention or resource sta…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by blackliner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Actions Build, test, and automate your deployment pipeline with world-class CI/CD other General topics and discussions that don't fit into other categories, but are related to GitHub
2 participants