New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sbc-bench on arm #4
Comments
The readme of this project clearly explains the four different usage modes:
The first three usage modes require the cpufreq governor being set to The last mode is for monitoring and doesn't alter the cpufreq governor. What you're asking for is an interesting area of investigation: how does the chosen cpufreq settings (governor + other settings like min/max cpufreq or stuff like Examples:
These issues can only be addressed by looking into details (the Active Benchmarking approach) and not by providing a tool that is meant to be operated in fire&forget mode. |
Recommendation - don't change the CPU governors on sbc-bench - can report what's in use, but by changing it, it's hard to tell if exploring this item for a/b testing
echo performance >/sys/devices/system/cpu/cpu${i}/cpufreq/scaling_governor
The text was updated successfully, but these errors were encountered: