On Monday 30 December 2024 21:51:29 Greenwich Mean Time Alan Grimes wrote:
Hey, I'm having usability problems in applications as my CPU clock
frequency crashes down to about 530 mhz... I need it lock in a floor frequency of 1.25 ghz... I used
cpupower frequency-set -d 1.25GHz which does lift it up to a usable frequency but a day later it crashes down to garbage again. The machine
is capable of 4.5 ghz or better on 32 cores. (it's a $3,200 processor, I shouldn't have to experience anything resembling a slowdown while the
load average is under about 128...)
Basically, if it's not about to catch fire, then I need it to honor that frequency floor.
You haven't mentioned which CPU you are using. If we're talking about AMD, then without diving into the weeds of the amd_pstate settings to understand
the combination and interactions of CPPC and Pstate with your chosen scaling governor, I wouldn't know why a day later your minimum frequency setting has been reset. I'd guess your scaling governor took over, but someone more studied on this topic can chime in.
From what I recall the userspace governor allows root to set the frequency statically by using a sysfs file. Other governors e.g. schedutil will scale down the frequency by sampling the current load and make suitable predictions on impending demand.
The next question is why it's even trying to scale down that low when
there are a bunch of threads running flat out trying to show me youtube
ads and crap. =\
Probably because a single thread plus some GPU cycles will process the youtube ads adequately, while the rest of the cores are not lifting any weight at the time. Setting a floor frequency for the CPU when it does not need it is both unnecessary and wasteful when any and all variations in frequency are being controlled as needed by the firmware. When I emerge big packages with all cores set in MAKEOPTS, I can observe individual cores boosting selectively for a few seconds before they drop slightly back waiting for their turn to max out again. I have noticed the same round-robin behaviour boosts CPU cores momentarily when running cpuburn and other load maximizing benchmarking software. I understand this is how the chipset algo controls the thermal load of the CPU. Some tweaking is offered by the BIOS firmware, but the general recommendation is to leave it alone to do its thing, unless you are trying to achieve some wild benchmarking record for bragging rights and the $3,200 price tag going up in smoke is not a significant consideration for you.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmdzMuMACgkQseqq9sKV ZxlVyg//UenH10PRH5237QDoHj4HjS2++KRzrM3qfJk3R0FNDjimbM8mIGQDEwtJ dDcUykdLrANfbeGrxqw0WbkLEpWhq9eShBfHqSvD3NjGYTDoMAwOefp6h0VHwS36 5FK/OQz5xsbreNi7+6FHPvVtm+SLfWLoE+arhl3yW4/gkVUO+oBX4uAndaHJahYX ZY28Hc9DAXJMA8ZQ2/Fkoa6fgIQp6EEef8zlO4zdQiCoPs1Rnn5WL9fyZhc0PcHD 9DyAvnmQGxzgBiCke/dJ7opBo5FcM+3s2MigkKYUP8gp6khT6hRIe+7OUl7+McQL zw5ZQtt3fMh9lsfJDryzk1H34CMXYBht/vsRbBbEZsgEapq/HwZfqxgd0Sxn5Zc+ 8NQyoS0AQyoo1i8A+Bqhp4fZtiEbpvDwHlaeG1M55xeMAu7whlineNeHGAyilHFv 7wZpycM2SsersQn7+P0IgydlSzhQLRCa2PkDFsLLIh0L7YaNqQ9S6omngWUTxy3r 83HnU1MksQyvZ6mXLYHARxKE+peMq1pP4P4ooxhn31LyC6WsdTQYjGUBWxkvWaLS mAloAqGhoDtedGwc7turug6DEPiPxhbhHymZggmXKsG6ScoMFcVqBewfhTgKAZFb xKh0/Vr+U5GOQfayH8kUniHxm/Elw9koQvY1cWPHc3WdnOotNRU=
=TwNF
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)