Bug 219526

Summary: A case for setting energy_performance_preference to balance_performance by default
Product: Power Management Reporter: Artem S. Tashkinov (aros)
Component: OtherAssignee: Mario Limonciello (AMD) (mario.limonciello)
Status: RESOLVED PATCH_ALREADY_AVAILABLE    
Severity: high CC: mario.limonciello
Priority: P3    
Hardware: AMD   
OS: Linux   
Kernel Version: Subsystem:
Regression: No Bisected commit-id:

Description Artem S. Tashkinov 2024-11-24 20:36:39 UTC
I would really love AMD to consider setting energy_performance_preference to balance_performance at least for laptops.

By default amd-pstate overshoots frequencies and makes power consumption significantly higher for simple tasks such as watching YouTube videos with HW acceleration turned on.

Here's a simple comparison:

Watching a VP9 1080p YouTube video in Firefox with HW acceleration turned on:

                  performance balance_performance
Watts                     14W                  7W
CPU frequency         5000MHz             3000MHz

In terms of sustained performance for tasks that require full CPU use, the difference is negligible.
Comment 1 Artem S. Tashkinov 2024-11-24 20:38:43 UTC
                  performance balance_performance
Watts                     14W                  7W
CPU frequency         5000MHz             3000MHz
Temps                     60C                 40C
Fan                      Loud      Barely audible
Comment 2 Mario Limonciello (AMD) 2024-11-24 22:51:40 UTC
Default policy is set by the firmware. It's overriden by userspace (power profiles daemon) based upon whether running on AC or battery.
Comment 3 Artem S. Tashkinov 2024-11-25 09:47:08 UTC
(In reply to Mario Limonciello (AMD) from comment #2)
> Default policy is set by the firmware. It's overriden by userspace (power
> profiles daemon) based upon whether running on AC or battery.

What stops you from overriding that?
Comment 4 Mario Limonciello (AMD) 2024-12-02 07:02:21 UTC
Technically?  Nothing.  It's a pretty trivial patch.

Let me discuss it internally with others at AMD to decide though.
Comment 5 Artem S. Tashkinov 2024-12-07 04:09:49 UTC
Thanks a ton for the patch!

Will be fixed in 6.13.
Comment 6 Mario Limonciello (AMD) 2024-12-07 04:30:24 UTC
Sure. But to clarify this will be 6.14 not 6.13.