Ok … well this was a big rabbit hole … Been reading lots of Docs (most outdated) and discovered you can play with any module that is listed in /usr/lib/modules/$(uname -r)/modules.alias … I think 
But these two caught my eye … as I understand it “acpi_cpufreq” should be available to any machine (could be wrong) … pcc_cpufreq errored out when I tried to use it … I think it’s because either
- I don’t have some option enabled in my bios (doubtful) or …
- My bios isn’t new enough
dart@windeath:~> less /usr/lib/modules/$(uname -r)/modules.alias | grep cpufreq
alias platform:acpi-cpufreq acpi_cpufreq
alias platform:pcc-cpufreq pcc_cpufreq
At any rate I tweaked my desktop-max profile to use acpi_cpufreq and got the best results so far with slight improvements over my previous posted profile … so here it is:
dart@windeath:~> cat /etc/tuned/profiles/desktop-max/tuned.conf
#
# tuned configuration
#
[main]
summary=Optimize for maximum desktop performance
[modules]
# non-zero -> strict ACPI checks are performed during frequency changes (0/1)
#acpi_cpufreq=+r,acpi_pstate_strict=0
acpi_cpufreq=+r
# removed from 6.14 ... left for older DESKTOPS but don't recommend it
# setting to 0 may cause problems as well
#[sysctl]
#kernel.sched_autogroup_enabled=1
[cpu]
priority=10
governor=ondemand|schedutil
sampling_down_factor = 1000
energy_perf_bias=performance|balance_performance
energy_performance_preference=performance|balance_performance
boost=1
[acpi]
platform_profile=performance
[audio]
timeout=10
[disk]
# Comma separated list of devices, all devices if commented out.
# devices=sda
readahead=>4096
# cat /sys/block/<device>/queue/scheduler
# current (6.14.4-1-default) none [mq-deadline] kyber bfq
# mq-deadline was my default but kyber seems to work the best for me
elevator=kyber
[scsi_host]
#
alpm=max_performance
If anyone can improve this profile please do … haven’t gotten to the networking part yet