(almost) Identical systems, different power consumption

crc-error-79

Member
Apr 10, 2023
62
4
8
Italy
Hello everybody,

I have 2 very similar Hp Elitedesk G4 mini, the first one on powertop can go on pkg (HW) up to C9, the second one is stuck at C2 and the power consumption in idle is near 5-6W higher than the first even with 0 vm running

Is there a way to check why the second doesn't get higher C-states?

Here is a short summary of both machine
- BIOS settings and version are the same (I exported the configuration and imported into the second)
- both have nvme crucial p3 1tb (same model and firmware)
- both have the same cpu i5 8500T
- both are in powersafe governor
- both are in all "good" on powertop tunable tab

The only difference is the ram. The fist has kingston ddr4 2666 2x16, and second Crucial ddr4 3200 2x16


powertop of the first

Markdown (GitHub flavored):
           Pkg(HW)  |            Core(HW) |            CPU(OS) 0
                    |                     | C0 active   8.0%
                    |                     | POLL        0.0%    0.0 ms
                    |                     | C1          0.8%    0.1 ms
C2 (pc2)    6.2%    |                     |
C3 (pc3)    1.3%    | C3 (cc3)    0.4%    | C3          0.5%    0.1 ms
C6 (pc6)    7.0%    | C6 (cc6)    8.1%    | C6          8.8%    0.6 ms
C7 (pc7)    0.0%    | C7 (cc7)   69.1%    | C7s         0.0%    0.0 ms
C8 (pc8)   16.4%    |                     | C8         34.9%    2.0 ms
C9 (pc9)    3.1%    |                     | C9          0.1%    2.2 ms
C10 (pc10)  0.0%    |                     |
                    |                     | C10        35.9%    4.8 ms
                    |                     | C1E         6.3%    0.2 ms

                    |            Core(HW) |            CPU(OS) 1
                    |                     | C0 active   8.8%
                    |                     | POLL        0.0%    0.0 ms
                    |                     | C1          0.9%    0.1 ms
                    |                     |
                    | C3 (cc3)    0.4%    | C3          0.5%    0.1 ms
                    | C6 (cc6)    7.8%    | C6          8.6%    0.6 ms
                    | C7 (cc7)   68.8%    | C7s         0.0%    0.1 ms
                    |                     | C8         31.2%    1.9 ms
                    |                     | C9          0.1%    2.6 ms
                    |                     |
                    |                     | C10        39.2%    5.3 ms
                    |                     | C1E         6.4%    0.3 ms

                    |            Core(HW) |            CPU(OS) 2
                    |                     | C0 active  11.0%
                    |                     | POLL        0.0%    0.0 ms
                    |                     | C1          0.9%    0.1 ms
                    |                     |
                    | C3 (cc3)    0.4%    | C3          0.5%    0.1 ms
                    | C6 (cc6)    8.4%    | C6          9.1%    0.7 ms
                    | C7 (cc7)   67.0%    | C7s         0.0%    0.1 ms
                    |                     | C8         28.1%    1.7 ms



powertop of the second

Markdown (GitHub flavored):
           Pkg(HW)  |            Core(HW) |            CPU(OS) 0
                    |                     | C0 active   1.5%
                    |                     | POLL        0.0%    0.0 ms
                    |                     | C1          0.1%    0.5 ms
C2 (pc2)   88.9%    |                     |
C3 (pc3)    0.0%    | C3 (cc3)    0.0%    | C3          0.0%    0.1 ms
C6 (pc6)    0.0%    | C6 (cc6)    1.0%    | C6          1.1%    0.8 ms
C7 (pc7)    0.0%    | C7 (cc7)   95.7%    | C7s         0.0%    0.0 ms
C8 (pc8)    0.0%    |                     | C8          3.7%    1.7 ms
C9 (pc9)    0.0%    |                     | C9          0.0%    0.0 ms
C10 (pc10)  0.0%    |                     |
                    |                     | C10        92.9%   17.1 ms
                    |                     | C1E         0.1%    0.3 ms

                    |            Core(HW) |            CPU(OS) 1
                    |                     | C0 active   0.5%
                    |                     | POLL        0.0%    0.0 ms
                    |                     | C1          0.1%    0.7 ms
                    |                     |
                    | C3 (cc3)    0.0%    | C3          0.0%    0.2 ms
                    | C6 (cc6)    0.1%    | C6          0.1%    0.5 ms
                    | C7 (cc7)   98.3%    | C7s         0.0%    0.0 ms
                    |                     | C8          3.8%    2.8 ms
                    |                     | C9          0.0%    0.0 ms
                    |                     |
                    |                     | C10        95.3%   40.8 ms
                    |                     | C1E         0.1%    0.3 ms

                    |            Core(HW) |            CPU(OS) 2
                    |                     | C0 active   0.8%
                    |                     | POLL        0.0%    0.0 ms
                    |                     | C1          0.2%    0.7 ms
                    |                     |
                    | C3 (cc3)    0.0%    | C3          0.0%    0.1 ms
                    | C6 (cc6)    0.1%    | C6          0.1%    0.4 ms
                    | C7 (cc7)   97.0%    | C7s         0.0%    0.0 ms
                    |                     | C8          3.7%    2.8 ms
 

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!