CPU Benchmarks and TDP

Kinda my view on this.

I can sustain 54 watts gaming… But only 42 when running a benchmark.

Temps are completely fine when gaming too… so… Im gonna roll with it.

Adding another 32GB of RAM didn’t change these values much. Now I’m at 14994 and 1724, temperature and power remain the same. So Cinebench 23 seems to not benefit from the second RAM-channel.
The power supply seems to have an influence, though. These values are with the 180W supply. If I use the Dell WD19DCS dock instead, the indicated power in multi-core was 35W only. Didn’t complete the test, though (each run takes 10 minutes).
All measurements with nvtop 3.1.0 and power set to balanced. Switching to performance, the multi-core result is slightly higher at 15135.

Running those benchmarks, I’m encountering a torrent of kernel messages from apparmor regarding nvtop:

[Apr19 13:11] kauditd_printk_skb: 1550 callbacks suppressed
[  +0,000008] audit: type=1400 audit(1713525062.784:20472603): apparmor="DENIED" operation="open" class="file" profile="snap.nvtop.nvtop" name="/proc/1/fdinfo/" pid=61026 comm="n>

How to get rid of these?

ekkehard@FW16:~$ sudo nvtop --version
nvtop version 3.1.0

I bet apparmor adds some more CPU cycles as the denial must be handled and logged.
Because I know my systems well, I tend to disable it when running on desktops. Usually the browsers are the ones causing issue.
On my servers, I let it enabled but make sure the profiles are updated correctly.

I don’t know apparmor. At all. I’ve been using linux on and off, but not on the desktop. I’m on Ubuntu 22.04 because that’s one of the two recommended and supported versions for the FL16. I’m on linux because I don’t want to endure M$ anymore.
My older linux machine is running mint, but that one is only used for compiling android.
Using a couple more CPU cycles I don’t mind, but spamming the kernel log I do.
So how to repair the rule that spawns these messages? nvtop is running with sudo, it should have all the permissions it could ever need.

oh right. because it’s the framework 16.
on every other laptop it’s the palmrest/top keyboard piece. Here I call it top cover rather than, but oh well. Names.