5105开启了CPU频率调节节能以后，13个小时的统计信息。

duany***

Linux pve 5.15.53-1-pve #1 SMP PVE 5.15.53-1 (Fri, 26 Aug 2022 16:53:52 +0200) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Sep 12 22:30:58 CST 2022 on pts/0
root@pve:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 2.00 GHz:0.15%, 2.00 GHz:0.01%, 1.90 GHz:0.01%, 1.80 GHz:0.01%, 1.70 GHz:0.02%, 1.60 GHz:0.02%, 1.50 GHz:0.03%, 1.40 GHz:0.04%, 1.30 GHz:0.07%, 1.20 GHz:0.15%, 1.10 GHz:0.42%, 1000 MHz:0.80%, 900 MHz:1.22%, 800 MHz:97.06%  (89262)
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 2.00 GHz:0.07%, 2.00 GHz:0.00%, 1.90 GHz:0.01%, 1.80 GHz:0.01%, 1.70 GHz:0.01%, 1.60 GHz:0.02%, 1.50 GHz:0.03%, 1.40 GHz:0.05%, 1.30 GHz:0.08%, 1.20 GHz:0.17%, 1.10 GHz:0.44%, 1000 MHz:0.85%, 900 MHz:1.32%, 800 MHz:96.94%  (95866)
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 2.00 GHz:0.09%, 2.00 GHz:0.00%, 1.90 GHz:0.01%, 1.80 GHz:0.01%, 1.70 GHz:0.01%, 1.60 GHz:0.01%, 1.50 GHz:0.02%, 1.40 GHz:0.04%, 1.30 GHz:0.07%, 1.20 GHz:0.15%, 1.10 GHz:0.42%, 1000 MHz:0.83%, 900 MHz:1.25%, 800 MHz:97.08%  (91262)
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 2.00 GHz:0.09%, 2.00 GHz:0.00%, 1.90 GHz:0.01%, 1.80 GHz:0.01%, 1.70 GHz:0.01%, 1.60 GHz:0.02%, 1.50 GHz:0.03%, 1.40 GHz:0.04%, 1.30 GHz:0.07%, 1.20 GHz:0.16%, 1.10 GHz:0.40%, 1000 MHz:0.80%, 900 MHz:1.22%, 800 MHz:97.14%  (88942)
root@pve:~#




CPU大部分时间在800MHZ,这样不知道对系统会有什么影响。

sean***

既然负载和cpu利用率都很低，为啥不关闭节能呢。低负载下高频和低频的功耗基本没有啥区别。

duany***

seanrigh 发表于 2022-9-13 10:54
既然负载和cpu利用率都很低，为啥不关闭节能呢。低负载下高频和低频的功耗基本没有啥区别。

减少发热呀。既然低频率都可以从容运行，长时间高频率有和意义呢？产生无用的热量？而且这个也不是说高频率不运行，有很少时间是自己调节到高频率运行的，如果关闭这个，CPU基础频率就是2G，一直再2G-2.9G之间运行，现在这样是在800Mz-2.9G之间自动调节，在跑分的时候自动睿频到2.9G

sean***

duanyu1979 发表于 2022-9-13 11:03
减少发热呀。既然低频率都可以从容运行，长时间高频率有和意义呢？产生无用的热量？而且这个也不是说高频 ...

给你说了，负载低的，高频低频的功耗基本没区别，功耗不就是发热，发热也没有什么区别。
我测试了1个多月，低负载下，固定最高频和节能睿频的长期运行功耗基本无差，最高温度基本只差2度。

当然前提条件是负载低，像你这种负载，再搞节能基本无意义。
既然开不开节能最终的功耗和发热都差不多，为啥不让系统高频运行呢？

duany***

还有我认为在cpu能力过剩的情况下，打开频率节能可以提高利用率减少能耗(频率高等于白白发热了），下图是我调节前后cpu利用率的差别。

duany***

seanrigh 发表于 2022-9-13 11:06
给你说了，负载低的，高频低频的功耗基本没区别，功耗不就是发热，发热也没有什么区别。
我测试了1个多 ...

本来就是一个10W最高功耗的CPU，2度发热也很可观了，既然不影响性能，那为什么不低频率影响呢？当然我说的是不影响性能的情况下，不知道这样会对性能有什么影响？

sean***

duanyu1979 发表于 2022-9-13 11:15
本来就是一个10W最高功耗的CPU，2度发热也很可观了，既然不影响性能，那为什么不低频率影响呢？当然我说 ...

你是做软路由吧？频率对性能的影响太大了。你自己不就有打开节能前后的CPU利用率。

duany***

贴一个系统的基本信息。。

duany***

seanrigh 发表于 2022-9-13 11:16
你是做软路由吧？频率对性能的影响太大了。你自己不就有打开节能前后的CPU利用率。

是做软路由，cpu利用率提高点不好吗？而且如果爱快和openwrt大负荷运行，cpu也会自动提高频率的，统计表上也很明显，并不是在低频率运行的。
你说的具体影响性能在怎么看出来的呢？有没有测试的方法？我也测测。

sean***

duanyu1979 发表于 2022-9-13 11:20
是做软路由，cpu率用率提高点不好吗？而且如果爱卡和openwrt大负荷运行，cpu也会自动提高频率的，统计表 ...

我也不懂，也不会测，你可以去问下爱快的技术人员。
我是问过。

RrF***

个人理解，频率高点降低占用好一些，除非温度或者其他因素有大影响。和服务器应该类似

ax***

感谢楼主分享，学习了

duany***

有大神来答疑解惑吗？