> In benchmarking we didn't observe much computational difference between the too once the CPU is fully loaded. However, cranking up or cranking down the load one will discover that the performance setting is more responsive than powersave.
this is exactly the problem in production environments; workloads can be 'bursty' which can see not-insignificant performance reduction when using powersave. Many enterprise users even go so far as to disable C-states (and ASPM, and APST, etc...).
> It makes sense to default to powersave for most scenarios, especially for laptop users.
for laptop users, yeah. I question if 'most scenarios' is accurate.
> In benchmarking we didn't observe much computational difference between the too once the CPU is fully loaded. However, cranking up or cranking down the load one will discover that the performance setting is more responsive than powersave.
this is exactly the problem in production environments; workloads can be 'bursty' which can see not-insignificant performance reduction when using powersave. Many enterprise users even go so far as to disable C-states (and ASPM, and APST, etc...).
> It makes sense to default to powersave for most scenarios, especially for laptop users.
for laptop users, yeah. I question if 'most scenarios' is accurate.