and when the firmware does throttle things, half of the frequency tools lie and claim the desired clock, not the actual clockOne difficulty with monitoring and logging a report is whether the drivers accurately report the speed the processor is running at.
The way I think it works is the Linux CPU governor suggests a clock speed based on system load. The driver tries to set that speed, but heat and power management considerations may prevent the CPU from running at the requested speed. What actually gets reported to the user depends.
"vcgencmd measure_clock arm" shows the true clock, while cpufreq shows the desired clock
a difference in those indicates throttling
but "vcgencmd get_throttled" i think it was, will also just tell you the answer immediately
Statistics: Posted by cleverca22 — Fri Jun 21, 2024 1:02 am