You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.
I run a benchmark on my Ubuntu Server "OVH EG AMD" but it reported my hexacore cpu max freq at 800MHz when it is 2.30GHz. This caused a low score, and I saw also other testers had this low score so they surely have my same issue.
The low score is true but it's due to a software bug of Ubuntu, not the server itself, and i think it's right to detect this situation and alert the user he can apply an easy workaround to this bug to achieve better server performance.
This was due to a cpufreqd package bug, more infos about it at:
Now I'm re running the test after applying the workaround (removing the -f in the /etc/init.d/cpufreqd) and I also give these manual commands before running the benchmark, I think you should add these to the benchmark scrpit
apt-get install cpufreqd cpufrequtils
service cpufreqd restart #check if it fails with core dump you have to fix init.d removing the -f option form the start _daemon command
cpufreq-set -d performance #set cpu at MAX frequency, now!
sleep 15
cpu-info #to check if it is now at max cpu freq, abort if not (there's some issue) please!!!!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I run a benchmark on my Ubuntu Server "OVH EG AMD" but it reported my hexacore cpu max freq at 800MHz when it is 2.30GHz. This caused a low score, and I saw also other testers had this low score so they surely have my same issue.
The low score is true but it's due to a software bug of Ubuntu, not the server itself, and i think it's right to detect this situation and alert the user he can apply an easy workaround to this bug to achieve better server performance.
This was due to a cpufreqd package bug, more infos about it at:
https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1162160
http://creativeprogramming.it/en/knowshare/item/52-cpu-frequency-scaling-issue-stuck-at-lowest-frequency-cpufreqd-issue
Now I'm re running the test after applying the workaround (removing the -f in the /etc/init.d/cpufreqd) and I also give these manual commands before running the benchmark, I think you should add these to the benchmark scrpit
The text was updated successfully, but these errors were encountered: