Enable performance CPU governor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
With some hardware, BIOS or OS settings, the CPU of a perfSONAR node can run under a CPU governor that will not provide the best performance to run CPU intensive tests, like high bandwidth throughput or high packet rate (O|T)WAMP tests. The CLI tools cpupower (on CentOS) or cpufrequtils (on older Debian/Ubuntu) can change that setting, but it doesn't persist after a reboot.
I think the pS toolkit, as part of its tuning scripts, should check and change the CPU governor of the OS it is installed on in a permanent manner. On CentOS this is done through a tuned configuration. See https://www.certdepot.net/rhel7-get-started-cpu-governor/ and https://www.certdepot.net/rhel7-apply-tuning-profile-server/ Under Debian we should check out this page: https://wiki.debian.org/CpuFrequencyScaling
This could also provide a benefit to some pScheduler high demanding operations and help in situations where tasks are being marked as overdue, missed or failed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.