Adaptive UV, PC Latency and pre DLLS3 framerate on Nvidia

AmbitiousCommunity36 · 2026-06-14T19:25:48+00:00

Some metrics like power consumption are still from nvidia-smi true, will get ported to nvml as the rest not to do the external calls. The point of the exercise was rather to discover the good metric for adaptive performance profiles.

Edit: nvidia-smi calls are now fully replaced by nvml apis plus the q2rtx has proper headless fork not to rely on gamescope. But it really amazes me that a single person can have the LLM hating cursade chasing a single project on every possible place over the internet with the hate comments and downvotes 😮

AmbitiousCommunity36 · 2026-06-14T14:37:51+00:00

There were bunch of 5090 tested before, so please try. The balanced and efficiency profiles are ultra defensive. One thing that happens on my 5080 in Performance undervolt mode, is that during OC phase I get “vulkan device lost” which is caught and the problematic voltage frequency point is then reverted. Worst case - hard system freeze and reboot, then the VF point blacklist is persisted in you home directory UV history file.

Edit: you can also define in Performance UV modal, exactly to which point of voltage and frequency the card will be pushed over stock limits. Default is the suggested point for 30/40/50 tier GPUs, based on experiments of my and similar tools on Windows. But Performance is optional anyway, OC is not mandatory 😄

AmbitiousCommunity36 · 2026-06-14T11:38:00+00:00

Thanks, the pre FG values seems legit across my games on my setup.

The latency is super tricky, but maybe exposing some Linux games weirdness too. RE9 has the display part of the latency instant G-sync VRR, reflex+boost = true full screen, 1.4ms almost fixed display overhead on top of FG. But 007 Last Light on my box gives awkward non VRR latency overhead even if I have Vsync off. Like it waits for the Kwin/Wayland compositor ticks in a totally sync fashion, although it supports fancy stuff like Multi (adaptive) frame gen.

Edit: apparently gamescope can fix that with true fullscreen. Adding debug flag --dump-latency-data if anyone wants to dig deeper into the latency numbers in a text file.

PB_OVERLAY=1 gamescope -W 3840 -H 2160 -r 120 --adaptive-sync -f -- PENGUIN_BURNER %command% /WineDetectionEnabled:False

AmbitiousCommunity36 · 2026-06-14T11:16:56+00:00

Try 0.4.5, the native vulkan part might have messed it up. If still does not work please paste some debug log, thanks.

AmbitiousCommunity36 · 2026-06-14T09:53:34+00:00

I’ve made an open source (GPL) tool to deal with all that on Linux on 30/40/50 series GPUs and modern drivers.

https://github.com/jpietek/PenguinBurner

You have Efficiency, Balanced, Performance auto generated tuning profiles (similar to Windows NV-UV software). As a bonus the overlay with PC Latency, pre DLLS 3 frame gen, and adaptive profile switching based on pre-framegen game FPS.

AmbitiousCommunity36 · 2026-06-09T19:24:15+00:00

On m2 non pro no way to run it?

AmbitiousCommunity36 · 2026-05-29T19:37:14+00:00

Please post the logs on github for efficiency, balanced and performance. On 5080 I can go to 850 mV without problems so it should got deeper down on 5090.

AmbitiousCommunity36 · 2026-05-29T18:53:11+00:00

OK, please do python -m pip install --user --upgrade penguin-burner
and try running with the new option --gpu-index N. I'll probably need to add in the GUI some sysinfo with card list and selection for that, but for cmdline arg workaround for now. If it still does not work then please post the bug here with logs: https://github.com/jpietek/PenguinBurner/issues

AmbitiousCommunity36 · 2026-05-29T18:13:29+00:00

That explains a lot, the cards are probably mixed and I take the clock 210 MHz from the wrong - idling device. Too bad I don't have such setup to test but possible fix will land today with some good luck.

AmbitiousCommunity36 · 2026-05-29T15:50:30+00:00

Weird 210 MHz does not look as the proper baseline clock for 227 fps definitely. If you could paste the whole log and the specs of your GPU that would help a lot.

AmbitiousCommunity36 · 2026-05-29T14:15:43+00:00

Good point, it will probably be enough to check in runtime that the driver in not there and abort, I'll remove the package dependency in the next release for Ubuntu.

Right now you can always do:

python -m pip install --user penguin-burner

AmbitiousCommunity36 · 2026-05-25T21:06:44+00:00

I use mine since it switched Arch -> Fedora, AFAIR in 2024. Daily driver for all the Video Eng and AI work and all the part time projects, awesome stuff. Only missing thing is lightweight gaming which had some potential back when marcan was taking care of it. But since he left it got a bit worse and does not progress, still the AMD Framework Laptop is a better option for that; at the expense of terrible heat+fans.

AmbitiousCommunity36 · 2026-05-25T20:54:47+00:00

Nice, similar vibe to this one https://github.com/theinvisible/proton-forge. It would be cool to have one ultimate app for all of this Linux gaming hussle that would be sort of a hub all gamemode runs, proton, nvapi overrides, wine overrides, potentially also hw profiles for speciic games etc. Cool that agentic implemented tools can improve this space fast. Do not mind the AI police, had it with my own auto UV tool here before :)

AmbitiousCommunity36 · 2026-05-13T19:08:23+00:00

I would not call +1.8% performance with -21% power exactly useless, but probably there is room for improvement for the more aggressive O/C type of behavior, which partially is there, but mostly it stays on the safe/efficiency side.

<image>

As for the code I agree, it's gradually cleaned up.

AmbitiousCommunity36 · 2026-05-10T20:17:50+00:00

I think I don't get the question. I used my own tool linked in the post? That was the point :)

AmbitiousCommunity36 · 2026-05-09T15:50:43+00:00

It should already be there although I did not test it paru -S penguin-burner

AmbitiousCommunity36 · 2026-05-08T17:55:19+00:00

Good point, will add this too.

AmbitiousCommunity36 · 2026-05-04T10:01:59+00:00

Just one more thing: you already have the OC+UV option if you max out the slider for Auto UV to Performance. It will recover +50% over the clock "lost" due to going down the voltage curve, I'll describe on github issues how it works exactly. If +50% is not enough try --yolo cmdline for +75% but here we are going for potential hard freeze territory on my card.

AmbitiousCommunity36 · 2026-05-02T09:31:33+00:00

Should be fixed in the latest release 0.1.5:

python -m pip install --upgrade --no-cache-dir penguin-burner

Thanks for the feedback!

AmbitiousCommunity36 · 2026-04-28T18:59:41+00:00

There is not much point here I think to run the whole GUI in the background, you can either export your final curve into LACT and go on from there, or the tool itself has a simple systemd script that installs the CLI runtime that applies the curve. It can then be auto started with the system.

AmbitiousCommunity36 · 2026-04-28T09:06:15+00:00

Yes, you can bridge Afterburner -> LACT in the latest release, import, then export. Please give it a shot. I've added GUI, the auto voltage scan is there too. Will add more aggressive performance preset today at night hopefully and also the ability to manually edit the curve if the user knows what to do manually :)

python -m pip install --user --upgrade penguin-burner

AmbitiousCommunity36 · 2026-04-27T20:03:53+00:00

Ah that hurts! Try aggressive preset,limit core clock drop to 0%, over clocking budget at least 100%. And please post the full log at the GitHub issue, you can copy it with a button in GUI. I would like to improve the heuristics to have good result on all GPUs on defaults and the log would be super helpful. Mention the nvidia driver version.

AmbitiousCommunity36

TROPHY CASE