Power saving with Intel P-States: not fully working

ocugin

New Member
Dec 4, 2023
1
0
1
germany
Hello all!

I suspended al reason an purchased a pile of hardware to set up my personal file server, just because i thought it would be good.
This ist the hardware:

MB Asrock Pro RS Intel H670
CPU Intel Core i5 13500
PSU be quiet Pure Power 11 400 W
SSD 1TB Lexar NM710 M.2
SSd 4TB Lexar NM790 M.2
RAM DDR4 Corsair 64GB (2x32) - One of them not working properly. Have to RMA.

I am using only the working one 32GB RAM atm.

My main issue is, that i really want to make this server run 24/7 with very low power consumption. But i can't get the power consumption below 23W with no guest VM running.
What i did until now:

- installed proxmox 8.1.3
- installed pihole in CT
- installed TrueNAS Core in VM
- installed Nextcloud inside of TrueNAS

- Tweaked BIOS settings:
+ Enabled CPU C-State support
+ Enbaled VT-d
+ Enabled PCIE ASPM support
- installed powertop and toggled all tunables
- Set CPU scaling governor to powersave (can only select powersave or performance)

With all this done powertop 2.14 shows this:
Pkg(OS) | Core(OS) | CPU(OS) 0 CPU(OS) 1 Powered On 0.0% | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms C1_ACPI 0.2% | C1_ACPI 0.1% | C1_ACPI 0.0% 0.0 ms 0.2% 0.4 ms C2_ACPI 0.7% | C2_ACPI 0.9% | C2_ACPI 1.7% 2.9 ms 0.1% 0.2 ms C3_ACPI 94.1% | C3_ACPI 93.7% | C3_ACPI 87.8% 69.5 ms 99.6% 68.3 ms RC6pp 0.0% | | | Core(OS) | CPU(OS) 2 CPU(OS) 3 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.5% | C1_ACPI 0.6% 2.0 ms 0.4% 0.2 ms | C2_ACPI 1.4% | C2_ACPI 0.0% 0.0 ms 2.8% 2.9 ms | C3_ACPI 94.8% | C3_ACPI 93.9% 107.3 ms 95.7% 98.4 ms | | | Core(OS) | CPU(OS) 4 CPU(OS) 5 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.3% | C1_ACPI 0.6% 1.5 ms 0.0% 0.0 ms | C2_ACPI 2.0% | C2_ACPI 0.7% 1.0 ms 3.2% 3.0 ms | C3_ACPI 92.8% | C3_ACPI 88.6% 70.2 ms 96.8% 124.5 ms | | | Core(OS) | CPU(OS) 6 CPU(OS) 7 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.5% | C1_ACPI 0.0% 0.0 ms 1.0% 1.7 ms | C2_ACPI 0.0% | C2_ACPI 0.0% 0.0 ms 0.1% 0.3 ms | C3_ACPI 82.1% | C3_ACPI 65.9% 135.7 ms 98.2% 32.6 ms | | | Core(OS) | CPU(OS) 8 CPU(OS) 9 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.1% | C1_ACPI 0.1% 0.3 ms 0.0% 0.2 ms | C2_ACPI 1.3% | C2_ACPI 2.6% 3.4 ms 0.0% 0.0 ms | C3_ACPI 60.2% | C3_ACPI 20.4% 35.0 ms100.0% 147.1 ms | | | Core(OS) | CPU(OS) 10 CPU(OS) 11 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.0% | C1_ACPI 0.0% 0.0 ms 0.1% 0.3 ms | C2_ACPI 1.0% | C2_ACPI 1.9% 3.3 ms 0.0% 0.0 ms | C3_ACPI 98.6% | C3_ACPI 97.3% 45.5 ms100.0% 147.1 ms | | | CPU(OS) 12 | POLL 0.0% 0.0 ms | C1_ACPI 0.1% 0.4 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 99.9% 102.9 ms | CPU(OS) 13 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 1.0 ms | C3_ACPI 100.0% 695.0 ms | | CPU(OS) 14 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1550.7 ms | | CPU(OS) 15 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 16 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 17 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 18 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 13 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 1.0 ms | C3_ACPI 100.0% 695.0 ms | | CPU(OS) 14 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1550.7 ms | | CPU(OS) 15 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 16 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 17 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 18 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms |

I gathered that apparently powertop 2.14 doesn't support c-states behond C3. So i checked:

/sys/devices/system/cpu/cpu0/cpuidle# ls state0 state1 state2 state3

To me that looks like the higher c-states are not available. But why? I am almost completely lost and inexperienced. Would really appreciate if someone could point me in the right direction.
 
Hello all!

I suspended al reason an purchased a pile of hardware to set up my personal file server, just because i thought it would be good.
This ist the hardware:

MB Asrock Pro RS Intel H670
CPU Intel Core i5 13500
PSU be quiet Pure Power 11 400 W
SSD 1TB Lexar NM710 M.2
SSd 4TB Lexar NM790 M.2
RAM DDR4 Corsair 64GB (2x32) - One of them not working properly. Have to RMA.

I am using only the working one 32GB RAM atm.

My main issue is, that i really want to make this server run 24/7 with very low power consumption. But i can't get the power consumption below 23W with no guest VM running.
What i did until now:

- installed proxmox 8.1.3
- installed pihole in CT
- installed TrueNAS Core in VM
- installed Nextcloud inside of TrueNAS

- Tweaked BIOS settings:
+ Enabled CPU C-State support
+ Enbaled VT-d
+ Enabled PCIE ASPM support
- installed powertop and toggled all tunables
- Set CPU scaling governor to powersave (can only select powersave or performance)

With all this done powertop 2.14 shows this:
Pkg(OS) | Core(OS) | CPU(OS) 0 CPU(OS) 1 Powered On 0.0% | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms C1_ACPI 0.2% | C1_ACPI 0.1% | C1_ACPI 0.0% 0.0 ms 0.2% 0.4 ms C2_ACPI 0.7% | C2_ACPI 0.9% | C2_ACPI 1.7% 2.9 ms 0.1% 0.2 ms C3_ACPI 94.1% | C3_ACPI 93.7% | C3_ACPI 87.8% 69.5 ms 99.6% 68.3 ms RC6pp 0.0% | | | Core(OS) | CPU(OS) 2 CPU(OS) 3 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.5% | C1_ACPI 0.6% 2.0 ms 0.4% 0.2 ms | C2_ACPI 1.4% | C2_ACPI 0.0% 0.0 ms 2.8% 2.9 ms | C3_ACPI 94.8% | C3_ACPI 93.9% 107.3 ms 95.7% 98.4 ms | | | Core(OS) | CPU(OS) 4 CPU(OS) 5 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.3% | C1_ACPI 0.6% 1.5 ms 0.0% 0.0 ms | C2_ACPI 2.0% | C2_ACPI 0.7% 1.0 ms 3.2% 3.0 ms | C3_ACPI 92.8% | C3_ACPI 88.6% 70.2 ms 96.8% 124.5 ms | | | Core(OS) | CPU(OS) 6 CPU(OS) 7 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.5% | C1_ACPI 0.0% 0.0 ms 1.0% 1.7 ms | C2_ACPI 0.0% | C2_ACPI 0.0% 0.0 ms 0.1% 0.3 ms | C3_ACPI 82.1% | C3_ACPI 65.9% 135.7 ms 98.2% 32.6 ms | | | Core(OS) | CPU(OS) 8 CPU(OS) 9 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.1% | C1_ACPI 0.1% 0.3 ms 0.0% 0.2 ms | C2_ACPI 1.3% | C2_ACPI 2.6% 3.4 ms 0.0% 0.0 ms | C3_ACPI 60.2% | C3_ACPI 20.4% 35.0 ms100.0% 147.1 ms | | | Core(OS) | CPU(OS) 10 CPU(OS) 11 | POLL 0.0% | POLL 0.0% 0.0 ms 0.0% 0.0 ms | C1_ACPI 0.0% | C1_ACPI 0.0% 0.0 ms 0.1% 0.3 ms | C2_ACPI 1.0% | C2_ACPI 1.9% 3.3 ms 0.0% 0.0 ms | C3_ACPI 98.6% | C3_ACPI 97.3% 45.5 ms100.0% 147.1 ms | | | CPU(OS) 12 | POLL 0.0% 0.0 ms | C1_ACPI 0.1% 0.4 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 99.9% 102.9 ms | CPU(OS) 13 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 1.0 ms | C3_ACPI 100.0% 695.0 ms | | CPU(OS) 14 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1550.7 ms | | CPU(OS) 15 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 16 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 17 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 18 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 13 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 1.0 ms | C3_ACPI 100.0% 695.0 ms | | CPU(OS) 14 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1550.7 ms | | CPU(OS) 15 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 16 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 17 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms | | CPU(OS) 18 | POLL 0.0% 0.0 ms | C1_ACPI 0.0% 2.0 ms | C2_ACPI 0.0% 0.0 ms | C3_ACPI 100.0% 1679.9 ms |

I gathered that apparently powertop 2.14 doesn't support c-states behond C3. So i checked:

/sys/devices/system/cpu/cpu0/cpuidle# ls state0 state1 state2 state3

To me that looks like the higher c-states are not available. But why? I am almost completely lost and inexperienced. Would really appreciate if someone could point me in the right direction.

See the explanation here:
https://askubuntu.com/a/1440073
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!