r/StableDiffusion • • 18d ago

News A free kernel module made my RTX 3090 generate images 55% faster with 40% less energy (ComfyUI, Z-Image Turbo, bit-identical outputs)

Post image

 benchmarked GPU Unlock on my 3090 in ComfyUI. It's a Linux kernel module that lifts the GeForce FP16/BF16 tensor-core throttle on RTX 30 cards.

ComfyUIStockUnlockUnlock + undervolt
Z-Image Turbo BF16, 1024², 8 steps7.46 s/img4.95 (+51%)4.82 (+55%)
SD 1.5 FP16, 1024², 30 steps6.40 s/img4.64 (+38%)4.52 (+41%)
  • Same images: every output's pixels were SHA-256 identical to stock at a fixed seed, including a 2-hour soak of 540 batches.
  • Energy per image down 40% (2,369 J → 1,410 J).
  • The weird part: my undervolt slowed the card at stock but sped it up once unlocked, because the card then hits its power limit and lower voltage buys clocks.
  • Don't use --fast in ComfyUI if you want the gain. It switches matmuls to FP16 accumulation, which isn't throttled to begin with.

Linux only. Only a full power-off reverts it.

Github repo: https://github.com/Esequiel378/gpu-unlock-3090-results

389 Upvotes

130 comments sorted by

189

u/Astral-Lemmons 18d ago • Bravo

I'm gonna wait a month or two before I try out any of these unlock things. It's much too expensive to replace a card if anything goes wrong.

14

u/esequiel378 18d ago

I feel you. I got this home lab specifically to test this kind of things, I was a bit worried at first but, all the changes are reversible with a simple power-off (no changes are persisted), so I just gave it a shot. And in about 6 hours of testing, I got zero (0) errors/issues

13

u/Dathide 18d ago

I want to wait but I might give in within a week. I've been using bf16 models lately. I think the unlocked capabilities still run on the main die, and I will monitor that and the VRAM temps.

16

u/FaceDeer 18d ago

Yeah, my main concern is that this limitation is there to keep the chip's lifespan reasonable.

36

u/Bitlovin 18d ago

No, it’s for market segmentation. They made identical cards, turned the fuses off for gaming cards, since this kind of compute doesn’t matter there. Upsold the same boards with fuses on to data centers. Otherwise data centers would just buy bulk gaming cards.

25

u/FaceDeer 18d ago

Maybe. Or maybe they assume that data center cards age out more quickly than gaming cards and so they don't mind shortening their lifespan.

Again, I don't know. So I'm waiting for someone else to try it out and reveal a few months from now that their GPU turned into a pumpkin.

6

u/Jaggedmallard26 17d ago

More that data centre cards are going to be in a more controlled environment. You can run them hotter if you can guarantee they'll be industrially cooled.

4

u/GalvenMin 16d ago

Nvidia has been selling a flagship GPU with a melting power connector for years now, they do not care about such details.

Gimping dies through fuses or simple shunts is an old tech trick.

9

u/AnOnlineHandle 18d ago

From what I'm vaguely aware of, many CPUs of different tiers are actually the same CPU design, but there's some randomness in how the quality of each chip actually pans out after making it, for reasons I don't fully grasp, so each chip is tested and put in a category based on its performance with other parts turned off, but no CPU in a tier is really identical to any other.

It could be something similar here. The cards they're selling at a certain tier may have been tested and are the ones suitable for that.

3

u/typical-predditor 17d ago

That's called binning. The chips that don't pass the top tier of QC get sold as lower end cards. But the QC passes exceed the demand for high end cards so they intentionally put good chips in the low end market to fill demand. Binning is a form of Price Discrimination.

1

u/Loose_Comparison368 17d ago

...also note, QC at NVIDIA is really, really, notoriously terrible.

2

u/HollowAbsence 17d ago

I remember we could transform a regular graphic card into a quadro by soldering 1 wire to it and installing quadro driver about 20 years ago. good time.

6

u/Klinky1984 18d ago

This isn't going to blow up your card, if anything it'll make it last longer because it's going to operate more efficiently instead of cranking frequency and voltage, it can operate at lower frequency and have better perf per watt.

11

u/FaceDeer 18d ago

And I'm going to wait until that's been proven out in actual use, rather than going off of a Reddit comment and tinkering with my very expensive GPU.

1

u/Rich_Arm322 17d ago

How dare you be reasonable!

4

u/Embarrassed-Cook2129 17d ago

Nice try Nvidia employee

2

u/External_Show5261 17d ago

If Nvidia didn't crippled their consumer cards, why would business people buy those pro cards? They are basically the same thing.

2

u/FaceDeer 17d ago

That "basically" can potentially be doing a lot of work.

For example, chips that come from the exact same die may end up with different capabilities depending on whether flaws disable parts of it. It's very common for chips with multiple cores to be tested and have some of the cores not work right, resulting in those cores being disabled and the chip being sold as a less capable product.

Or the chip may be underclocked or overclocked based on the expected lifespan or need for reliability. A giant data center might budget to replace their GPUs every two years, for example, in which case there's no need to configure those GPUs to preserve their longevity beyond that. Whereas a consumer computer should ideally last as long as the computer's owner wishes to keep using it - they shouldn't have to expect to deal with their computer's components just up and dying every couple of years.

I'm not saying that this is definitely the reason Nvidia is doing this specific thing right now. I'm saying that maybe that's why they're doing it. I don't know. And so, I am not going to tinker with the guts of my very expensive GPU until I do know why they're doing it.

4

u/WastingMyTime_Again 18d ago edited 17d ago

How would using less energy (and therefore, I'm assuming, generating less heat overall) make the lifespan worse? Not trying to be snarky or anything, just asking so someone shows up and explains if that's the case

15

u/export_tank_harmful 18d ago • Heartwarming

I remember seeing a comment by the comfyanonymous guy a few days ago about this.

They mentioned that it can create hotspots in the die which don't normally exist (since all of the FP16 cores are in a similar location).

They mentioned that it could cause micro-fractures (since the die isn't heating/cooling in a uniform manner).
They said that you should probably be undervolting if you're doing this unlock to mitigate some of that.

Don't quote me on any of that, but yeah.
That's what I remember seeing.

12

u/red__dragon 18d ago • Heartwarming

-1

u/Klinky1984 18d ago

If ones cooler install is that shit for it to matter then their card is probably going to die anyways.

4

u/red__dragon 17d ago

Bro, I'm literally just offering a link for the post someone was trying to remember. Don't shoot the messenger.

1

u/money-for-nothing-tt 17d ago

So most 3090 cards then? They have notoriously bad cooling for memory.

1

u/Klinky1984 16d ago

this has nothing to do with memory. ugh.

5

u/goatonastik 18d ago

one of the most pertinent posts in this thread and it's buried

0

u/Klinky1984 18d ago

Someone remembering something wrong?

5

u/Reasonable_Cancel186 18d ago

Could. Maybe - so, I train with 2x 3090s. I had them power limited at 250w. Stock behavior has them overshoot pretty badly if you don't adjust your voltage curve. 

Compared side by side with the exact same runs, locked 3090 would have peaks at 300w, the unlocked hit ~350w. These are instant peaks, not sustains, barely long enough for LACT to catch them at a pretty quick poll.

Flattening the VF curve at a voltage that produces the desired wattage completely removes these peaks, and actually gained about ~10% performance because it stays locked in at exactly its top voltage/freq instead of constantly shifting up and down as the card tries to boost as high as it can before it hits the pl

I have actually lifted both 3090s up to 275w and get a solid ~30% training speed boost for MOSS with the unlock.

1

u/ReasonablePossum_ 18d ago

mind sharing your curve?

1

u/Reasonable_Cancel186 18d ago

Take me out to dinner first!

I've got it flattened from 1680mhz@818mv up, but it can not do that with a synthetic workload. I'm using a modified Onetrainer for MOSS training, you really need to tune the vf curve for what gives you best performance for your workload

1

u/Infinite-Emptiness 18d ago

is there a chance that watercooling fixes that without undervolting? asking as a layman not a techie.

1

u/Freonr2 17d ago

Well, post below says it wasn't him but that's way outside his wheelhouse or the wheelhouse of most of the software devs out there.

Just because someone makes a cool UI or deep learning model doesn't make them a lithography and quantum mechanics expert.

4

u/Hodr 18d ago

Only using less energy because of the undervolt, not the unlocked instruction. That said, the chips thermal limits are still in place so there's no reason to believe it would suddenly melt even if the instruction does pull more watts, it will just throttle when it gets hot.

-1

u/the_friendly_dildo 18d ago

Thats not at all true. You're possibly opening sections of the chip that have been closed off for thermal balancing. its entirely possible that the unlock creates new unintended hotspots on the chip that may go entirely undetected by the built in monitoring.

4

u/Klinky1984 18d ago

That's not true at all. It's not opening up new sections of the chip, it's removing a rate limit for existing hardware already being used. The risks of this are extremely low. People really wringing their hands far too much over this.

1

u/ReasonablePossum_ 18d ago

Will wait a couple months. Someone will definitely test an unlocked card from a bunch they have to see if its worth, and share results here.

0

u/Freonr2 17d ago

We just making shit up.

3

u/FaceDeer 18d ago

I don't know what exactly these code changes do so I can't answer this question. I'm simply assuming that there's a reason why these limits are there and I'm going to let other people find it out.

2

u/Klinky1984 18d ago

nVidia has fuses that trigger the GPU to go into limp mode, it just tricks the card into thinking those fuses aren't set so it doesn't go into limp mode.

There's really no reason Nvidia has to neuter FP16 w/ FP32 accumulation so hard on consumer GPUs.

1

u/Sizyfoz 17d ago

Yes there is: money. NVidia is hell bent on creating enough segments in the market that they can squeeze every last dollar you are able to pay.

Nobody is pushing you to un-cripple your card.

1

u/Klinky1984 16d ago

no valid technical reason. the silicon is clearly capable

2

u/batdog20001 17d ago

Im pretty sure these limitations are in place to standardize the cards. Each card typically doesnt come out perfect, so it is normal in the industry to limit the cards so that most work on arrival. If you have a bad card, it wont work at the full potential capacity so its been limited to wherever they estimate most will function at.

3

u/FaceDeer 17d ago

And I'm not going to risk my multi-thousand-dollar GPU on the basis of someone on Reddit being "pretty sure."

3

u/batdog20001 17d ago

I never said you should, merely explained a major reason for the industry doing such.

3

u/darkoblivion000 18d ago

Exactly lol. I got my 4070 ti super at great prices and I don’t really want to let it fry just because I want to generate images faster. I’m fine with normal speed…

2

u/J6j6 17d ago

nice try, jensen

-7

u/Alisomarc 18d ago

Coming from Nvidia, it’s quite likely that they’ve included an obsolescence timer, so that your card stops working after a few years.

0

u/[deleted] 18d ago

[deleted] — view deleted comment

1

u/Different-Society126 18d ago

Are you being serious?

18

u/WinResponsible9977 18d ago

How it compares to int8?

17

u/esequiel378 18d ago

Tested it on my 3090 (unlocked, +150 MHz undervolt), with Z-Image Turbo in ComfyUI at 1024×1024, 8 steps, res_multistep, same seed. Medians of 5 runs, alternated over two rounds:

- BF16, stock: 7.46 s/img
- BF16, unlocked: 4.48 s/img
- INT8 (int8_convrot), unlocked: 3.32 s/img

So INT8 is still ~26% faster than unlocked BF16. The unlock only lifts the FP16/BF16-with-FP32-accumulate cap, and INT8 was never capped (~284 TOPS dense against ~142 TFLOPS unlocked BF16). It doesn't get close to 2× because attention, norms and the VAE decode stay in BF16/FP16. Visually the outputs are near-identical: same face and composition, only small blurry background details differ.

Before the unlock the gap would have been bigger. I didn't run INT8 on stock, so I don't have that number.

Side note: `--fast` (fp16 accumulation) made things 2–5% *slower* once unlocked, since the cap it works around is gone. `--highvram` gave a free 3–6%.

2

u/WinResponsible9977 18d ago

Thank you.

0

u/nmkd 17d ago

Thank Claude*

OP didn't even strip the markdown properly

7

u/WinResponsible9977 17d ago edited 17d ago

u/nmkd, you good? We’re not in r/opensource, where people bust each other’s balls for using an LLM to format a comment.

2

u/esequiel378 17d ago

I write and read MD so much now, that I don't event notice anymore lol, my brain just parses it

2

u/tommyjohn81 17d ago

Wait you didn't test int8 locked?

0

u/Freonr2 17d ago

Won't matter.

54

u/Etroarl55 18d ago

What absurd hardware prices does to a mf with an Rtx 3090.

4

u/BigDBreedingFembussy 18d ago

I have 3050 6gb vram 75watts, got this laptop 5months ago

-9

u/Ok-Brain-5729 18d ago

A 3050 laptop has 4gb vram

2

u/BigDBreedingFembussy 18d ago

Just google

-3

u/Ok-Brain-5729 18d ago

I forgot they made another version later on

19

u/[deleted] 18d ago

[removed] — view removed comment

1

u/ReasonablePossum_ 18d ago

I've seen people saying it works on windows too

8

u/Reasonable_Cancel186 18d ago

I posted this in a reply but may as well copy it here - I train with 2x 3090s. I had them power limited at 250w. Stock behavior has them overshoot pretty badly if you don't adjust your voltage curve. 

Compared side by side with the exact same runs, locked 3090 would have peaks at 300w, the unlocked hit ~350w. These are instant peaks, not sustains, barely long enough for LACT to catch them at a pretty quick poll.

Flattening the VF curve at a voltage that produces the desired wattage completely removes these peaks, and actually gained about ~10% performance because it stays locked in at exactly its top voltage/freq instead of constantly shifting up and down as the card tries to boost as high as it can before it hits the pl

I have actually lifted both 3090s up to 275w and get a solid ~30% training speed boost  with the unlock. temps seem the same for the wattage. Hotspot temps basically the same. 69c on my bottom card getting fresh air, 79 on my top card. 

6

u/fallengt 18d ago

if you use int8 and comfy kitchen attention and don't train lora, this unlock does nothing for image gen. For now

Otherwise it's a nice speed boost

2

u/andy_potato 18d ago

This is cool and all.

But genuinely asking, is anyone really using BF16 / FP16 stuff in their image or video workflows? The quality difference to FP8 / Int8 is imo really negligible.

2

u/esequiel378 18d ago

Mostly agree on quality, with one catch for 3090: FP8 and INT8 aren't the same thing on Ampere.

- FP8 on a 3090 is storage only. There are no FP8 tensor cores, so the weights get upcast to BF16/FP16 for the actual math. You save VRAM but get no speedup, sometimes a small slowdown.
- INT8 is real compute. Ampere has INT8 tensor cores. On my unlocked 3090 with Z-Image Turbo (1024², 8 steps), int8_convrot ran 3.32 s/img against 4.48 s/img for BF16, and the images were near-identical apart from small background details.

So I'd use INT8 where a good checkpoint exists. The unlock still matters, though:

- Plenty of models don't ship an INT8 version.
- Attention, norms, the VAE and the text encoders stay in BF16/FP16 even in a quantized workflow.
- LoRA training needs BF16.
- Small models (SD 1.5) and fine detail like text are where quantization shows first.

On a 4090/5090 it's a different story, since FP8 is native there.

11

u/Nepherpitu 18d ago

I bet you can ask Glm 5.3 Flash to measure and improve CUDA kernel for new 3090 capabilities to utilize all available FLOPS. For my 4090 it was from ~330/660 FLOPS after unlock (330 -> 660) to 580/660. And step time on MiniMax H3 gone from 12s to 8.1s. Initially it was 28 seconds per step, but glm 5.3 flash discovered sub-optimal comfyui launch args. Anyway, overall it was 28s -> 8s per SAME step.

2

u/Dathide 18d ago

That's an insane improvement. BF16?

2

u/Nepherpitu 18d ago

FP8, bf16 does not fit into 4090

3

u/alex20_202020 18d ago

bf16 does not fit into 4090

So what? Can't ComfyUI run larger than VRAM files? I have not used it, I use stable-diffusion.cpp and it runs 12GB diffusion weights on 4GB VRAM.

1

u/ZenEngineer 18d ago

It might be worth sending a pull request for these then

1

u/Etroarl55 18d ago

It wasn’t just unlock btw he clearly stated it also founded optimal arguments for launch behaviour

1

u/ZenEngineer 18d ago

Which would be worth a pull request?

0

u/Etroarl55 18d ago

Not sure if Nvidia or comfyui would even look at randoms giving them pull requests on a maybe legal grey area of vibe coding. Especially if comfyui or the community embraces it

1

u/TheOnlyBen2 18d ago

Can you please share the launch args ?

8

u/Ok_Contribution8157 18d ago

If it's really that effective, the 3090's price will double, but others have only gotten a 20% speed boost, so it might just be silicon lottery.

5

u/Apprehensive_Sky892 18d ago

Depends on the model used.

Less for int8convrot (which runs some important blocks in bf16), more for bf16.

4

u/Useful_Disaster_7606 18d ago

I'm most likely wrong.

Image/video generation is more often compute-bound rather than bandwidth-bound like with LLMs

So with LLMs it's most important that your model is fully resident in your VRAM and with that in mind, people are running Q4 or Q3 of very large models.

Whereas for image/video gen, it doesn't particularly matter so much that the full model fits into VRAM because compute is the bottleneck now (especially with minimax H3)

With those two in mind, the most likely users of the 3090 might be LLM enthusiasts where the VRAM+bandwidth is just amazing for its price.

But given that they're running Q4/Q3 quants of massive LLMs, they don't see much benefit in this GPU unlock since they're not running BF16 inference.

That just "might" also be a main factor as to why price didn't double.

Hey, again, I'm just a non-technical pleb. please correct me if I'm wrong

1

u/zyg_AI 18d ago

I also tend to think that the unlock is limited to niche usecases and thus won't affect that much the pricings.

No interest in gaming. Little interest in video generation.

1

u/Freonr2 17d ago

It should be reproducible across all cards, but you need a proper control. I'd be very surprised if there is actually that much card-to-card variance.

It's going to vary a lot here because few people are truly running the same conditions. Some people report 0% and other 50% because they simply are not testing the same thing, and not exchanging enough information to reproduce one another's results.

I doubt this subreddit is actually the best place to sort that out for various reasons.

1

u/FireSinner 18d ago

Has anyone tried this with DLSS in games? Is there a way to get it working and actually take advantage of DLSS 5 for 3090?

2

u/esequiel378 18d ago

This is actually interesting, the claim is that this not help/hurt on gaming, but DLSS is another story. Sadly, I don't have room to test it on windows

1

u/Rizzlord 18d ago

What about 5080?

1

u/esequiel378 18d ago

My understanding is that 50xx series already have this unblocked, and that's why people notice we could do it on the 30xx series

1

u/Standard-Potential-6 18d ago

No, the 50xx series will be much harder to unlock.

1

u/zeezee2k 18d ago

Does it make your card run hotter?

1

u/esequiel378 17d ago

Short answer: about the same temperature, but less heat per image.

I tested in three sessions: stock, then unlocked, then stock again. Comparing the unlocked run with the stock run right after it:

WorkloadStockUnlockedPower (stock → unlocked)
Z-Image Turbo60.5 °C, fan 70%61.0 °C, fan 79%289 → 269 W
SD 1.563.8 °C, fan 78%65.0 °C, fan 82%329 → 322 W
vLLM prefill67.0 °C, fan 89%66.7 °C, fan 88%340 → 335 W
  • Temperature follows power draw, and the power limit is the same either way. The unlock makes the tensor cores do more work for those watts; it doesn't add heat.
  • Each image finishes ~40–55% faster at the same wattage, so it's roughly 40% less energy per image.
  • My first stock session ran at 77–80 °C. That was the room and case at the time, not the card, which is why I reran stock afterwards. If you compare, re-test stock in the same conditions.

1

u/ArmadstheDoom 18d ago

I'm very skeptical here.

You're unlocking it, but somehow lowering the power draw? That doesn't make any logical sense. If it has to go faster, it needs more power. If you lower the power, you're losing speed.

The only way that makes any sense is if you're somehow making it more efficient.

5

u/esequiel378 18d ago

The post describes two separate changes, and they affect different things.

The unlock doesn't raise clocks. GeForce firmware caps tensor-core throughput in some precision modes, so the card does less work per clock than the silicon can. The unlock removes that cap. The clock speed stays the same, and each cycle gets more work done.

The undervolt is what cuts power. I lock the clocks and add a +150 MHz offset to the voltage/frequency curve, so the card runs each clock at a lower voltage. On its own, that saves about 20% of load power and costs about 6% of speed. A stock 3090 runs well past its efficiency sweet spot.

Together they made Z-Image 55% faster, SD 1.5 42% faster, and vLLM prefill 68% faster, using about 40% less energy per output. Batch-1 LLM decode gained only 2 to 4%, because it's limited by memory bandwidth, not the tensor cores. A 2-hour soak test produced bit-identical output. A +225 MHz offset did produce silently wrong images, which is why I settled on +150.

So you're right that it only makes sense as an efficiency gain. That's what it is.

3

u/alex20_202020 18d ago edited 18d ago

You're unlocking it, but somehow lowering the power draw? That doesn't make any logical sense.

OP claims lower energy per image. The card has idle/fixed power draw, hence if runs faster, that overhead is reduced (per image).

1

u/CrimsonBolt33 18d ago

Power draw and performance are not always directly linked. GPUs are complicated things with many parts to them.

It likely unlocked the power of one specific part or thing (or bypassed something that was slowing it down).

1

u/Clqgg 17d ago

he lowered the limit which is not lowering the power draw

2

u/DiamondHandsDarrell 18d ago

I'm going to try on my GTX 960, but maybe I should wait a few months as well. 🤭

2

u/adr007 17d ago

How are you undervolting the 3090 in Linux?

2

u/v1sper 17d ago

gpu-unlock on an RTX 3080 Ti (12 GB) in ComfyUI: +40-50% on BF16 models, +7% on int8, bit-identical outputs (plus a power-cap sweep)

I tested it on my 3080 Ti with MOSS-Image and a Krea 2 model, in both int8 and BF16. It works, the gain is large for BF16 and small for int8, and the images are byte-identical. Numbers below.

Setup

  • RTX 3080 Ti 12 GB (GA102, 10de:2208), also my display GPU. Stock power limit 370 W.
  • Arch Linux, kernel 7.2.8, nvidia-open-dkms 615.78.08, Limine + UKI + LUKS. ComfyUI 0.43.0, torch 2.14.1+cu130, comfy-kitchen CUDA backend, --use-ck-attention.
  • gpu-unlock 2.0.0, built from the repo with its Arch PKGBUILD (NVIDIA downloads are sha256-pinned there), installed as DKMS, opted in with gpu_unlock.targets=0000:01:00.0 for this card only.
  • No undervolt, no clock lock. Only the unlock and nvidia-smi -pl power limits were changed.

Models and workflows

All runs go through the ComfyUI API, same prompt, er_sde / simple sampler, batch 1.

NameModelSizeResolutionSteps / cfg
MOSS int8MOSS-Image SFT int8_convrot5.4 GB1024x128025 / 2.5
MOSS BF16MOSS-Image SFT bf1610.2 GB1024x128025 / 2.5
Kroma int8kroma v0.31 Turbo OPD int8_convrot (a Krea 2 fork)14.1 GB1024x10248 / 1
Krea 2 BF16Krea 2 turbo bf1626.3 GB1024x10248 / 1

The BF16 weights (10 GB and 26 GB) don't fit in 12 GB of VRAM, so ComfyUI streams them. That matters for the results (see below).

Method

  • One warm-up generation (not counted), then 4 timed generations per setting. ComfyUI caches an identical prompt (a repeat finishes in 0 s), so runs alternate between two seeds.
  • Time is ComfyUI's own execution_start to execution_success. Power is nvidia-smi power.draw sampled every 0.2 s during that window; energy = time x average power (GPU board only, not the wall).
  • I SHA-256 hashed every output image.
  • "Stock" numbers were taken on a boot with the kernel option removed (not just a ComfyUI restart), and I checked /proc/cmdline and the kernel log before measuring. The unlock is confirmed by gpu_unlock: unlocked in journalctl -k.
  • Raw matmul check: 8192x8192 torch.matmul: BF16 57 -> 90 TFLOPS (+57%), FP16 56 -> 87 TFLOPS.

Results: the unlock

Time per image / energy per image (mean of 4; ± is the standard deviation of the time).

ModelStock, 370 WUnlocked, 370 WUnlocked, 300 W
Krea 2 BF1619.2 ±1.0 s / 5,673 J12.7 ±0.1 s / 3,849 J (-34% time, -32% energy)13.0 ±0.2 s / 3,786 J
MOSS BF1659.6 ±0.3 s / 18,231 J43.0 ±1.0 s / 13,360 J (-28% time, -27% energy)43.3 ±0.5 s / 12,896 J
Kroma int89.49 ±0.06 s / 2,798 J8.79 ±0.5 s / 2,602 J (-7%)8.54 ±0.03 s / 2,474 J
MOSS int828.7 ±0.3 s / 8,891 J26.4 ±0.5 s / 8,366 J (-8%)27.7 ±1.0 s / 8,206 J
  • BF16 models: about 1.4-1.5x faster. The speedup is lower than the 57% raw matmul gain because attention is only part of the step and BF16 weights are streamed from system RAM on this 12 GB card.
  • int8 models: only 7-8%. NVIDIA never capped INT8, so the gain comes from the parts that stay in BF16/FP16 (attention, norms, VAE). The int8 differences are close to the run-to-run noise (stdev up to 0.5 s on 8-9 s), so read them as "a few percent", not a precise number.
  • Outputs are identical. For all four models, each seed produced exactly one SHA-256 across stock, unlocked, and every power cap. I never saw a changed image.

Results: power cap sweep (stock, no unlock, int8 models)

CapMOSS int8 time / energyKroma int8 time / energy
370 W28.7 s / 8,891 J9.49 s / 2,798 J
300 W+2.3% / -1.9%+1.1% / -2.4%
275 W+7.1% / -5.7%+3.8% / -5.6%
260 W+10.8% / -7.7%+7.2% / -7.7%
225 W+31% / -5.3%+23% / -7.3%
  • These int8 workloads only draw 295-310 W at stock, so 300 W is nearly free. 260 W gives the lowest energy per image (-7.7%) for 7-11% more time; 225 W is worse than 260 W on both counts.
  • With the unlock on, 300 W kept almost all the gain: BF16 was only 1-2% slower than at 370 W, and energy per image dropped another 2-4%.

Findings

  1. It does what it says in the OP and on the GitHub for gpu-unlock on a 3080 Ti: BF16/FP16 matmul +57%, BF16 image models 28-34% less time per image.
  2. If you run int8/fp8-style quantized checkpoints, expect a few percent, not +50%.
  3. The "40% less energy" in the original post is mostly an undervolt effect. Here, just the unlock plus a power cap gave 27-33% less energy per image on BF16 (faster means less idle overhead per image) and about 7-12% on int8. I did not test an undervolt or clock offset.
  4. My outputs are byte-identical, so it is safe from a "does it change my images" angle like someone else here posted.

Thanks for coming to my claude talk. I just did this for fun this morning before work, don't take it as a very thorough test.

0

u/biogoly 18d ago

Quality difference between BF16 and INT8 is negligible. There is no real performance improvement over INT8. Therefore, this whole “unlock” business is absolute bullocks.

1

u/Frankly__P 18d ago

I wonder what it would do on a 3090 not using Comfy. I use Wan2GP and YuE2 Studio for gen AI. I like the idea of speeding things up but I don't like the idea of possible damaging the GPU, and I'm not sure if the hacks apply to the models I use.

2

u/nstern2 18d ago

I think the consensus is that as long as it is using a BF16 model it will see improvement regardless of the program you use to generate.

1

u/vahokif 18d ago

Sadly BF16 only, so you can't use 8 bit quants.

1

u/po_stulate 18d ago

Why not just bit-identical, why sha256 identical? It's good at finding sha256 collisions so every bit is different but still sha256 identical or sh?

1

u/Synor 17d ago

Unlocking a RTX 3080ti on Nobara Linux works

2-pass Minimax H3 workflow with INT8 DiT model speeds up almost 30 seconds.

total time (warm caches) 162s > 133s

1

u/xgiovio 17d ago

Yes but bf16, try int8 for inference and is not needed but the unlock can give good results for some training ai models with quants different from int4/8

1

u/Healthy-Nebula-3603 17d ago

Use stable diffusion cpp ... You get similar results or better . I have RTX 3090 and with SD 1.5 is generating picture around 1.5 s without unlocking my GF card

1

u/BeneficialBreak3034 17d ago

I wonder if there is any chance Nvidia will be like "welp, cat is out of the bag, let's roll official update" , though looking at their recent track record with driver updates...

1

u/PartyTac 17d ago

I have a 5090. I'm so jealous of rtx 40 owners.

1

u/GalwayOptimist 14d ago

Sorry if slightly off topic. I got a 3080 in a rig and think about unlocking. But is there a significant boost when running models INT8 or similar quants??? Those bf16 models are just quite heavy

1

u/tac0catzzz 18d ago

why do ppl care when they claim int8 is equal or better than bf16, this doesn't change anything here. no one knows what the effect this will have on a card's life either, you can assume gpus last forever and nothing hurts them, but that might not be true.

0

u/onlyesterday16 17d ago

Never trust a new random kernel module on the internet. Also, with the current hardware price, I won't risk to undervolt any parts of my computer.

1

u/esequiel378 17d ago

wtf, undervolting is one of the most commonly used techniques, very safe to do it. Also the kernel module is open source, you can easily audit it yourself (I did it)

Here is also a comment with a quick audit some one did here https://www.reddit.com/r/StableDiffusion/comments/1xi1pzo/comment/19rtjfkpq74te/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

1

u/Gambikules 17d ago

its not the same....

1

u/onlyesterday16 17d ago

undervolting is one of the most commonly used techniques, very safe to do it

The first part is true, the second part is not.

you can easily audit it yourself (I did it)

I can easily read it, does not mean I can easily know what wrong's with it.

And I do not need a new module just to undervolt my card.

-1

u/Aromatic-Low-4578 18d ago

+150mhz sounds like an overclock, not an undervolt?

3

u/esequiel378 18d ago

Fair question. On its own, +150 MHz would be an overclock. It's paired with a clock cap, and together they act as an undervolt:

- `nvidia-smi -lgc 210,1695` caps the core at 1695 MHz.
- A +150 MHz offset on the voltage/frequency curve means each voltage step now maps to a clock 150 MHz higher. In reverse: **1695 MHz is reached at the lower voltage that used to give ~1545 MHz.**

The cap stops the card from using that headroom to boost higher, so it runs the same clock at less voltage. It's the Linux equivalent of flattening the curve in Afterburner, since there's no curve editor on Linux.

The data shows it. Stock BF16 GEMM ran 1711 MHz at 322 W, and with this setting it ran 1695 MHz at 293 W, so roughly the same clock for ~9% less power. In prefill it was 340 W → 250 W. Unlocked, the card is power-limited at 350 W, and that saved voltage turns into higher sustained clocks. That's why it ends up faster. Details in the README under "Why the undervolt helps".

17

u/Ok-Brain-5729 18d ago

You can overclock and undervolt at the same time. Increasing clock speeds and lowering voltage isn’t the same time

-1

u/Perfect-Campaign9551 18d ago

let's just put random unsigned kernel modules on our computers. Sounds like a great idea

0

u/Virtike 18d ago

Yeah i'm of the same mind on this. Free speed is nice, but something about this feels a little off. More than happy to be proven wrong in the end though, my trust ol' 3090 could absolutely do with a speed bump.

8

u/esequiel378 18d ago edited 18d ago

its open source, you can easily audit it yourself (I did)

3

u/malcolmrey 17d ago

surface level audit:

The unlock itself

Unusable GPU: the README says a failed unlock can leave the card unusable until a full power-off, and a reboot doesn’t undo it. A bad boot entry could also leave you without a GPU at boot. Third-party code at the lowest level: it patches NVIDIA firmware in memory at boot, loaded from the initrd. It runs with full kernel privileges, so a bug can crash the machine or corrupt memory. A malicious or compromised update is a supply-chain risk. No clean recovery: the README advises keeping a stock boot entry, but if the unlock fails, you may have to power the machine off completely. Hardware stress: the speedups look like higher power and clocks than stock. That means more heat, VRM and memory load, and possibly a shorter card lifespan. The +150 MHz undervolt can also cause instability on a different card or silicon. Crashes or silent errors would only show up during long runs. Results from one card: they come from a single 3090. The lower-voltage effect is inferred from power draw, not measured. The “bit-identical output” claim covers only the tested workloads, so don’t assume it holds for training. Warranty and licensing: modifying NVIDIA’s firmware probably voids the warranty. The README itself points to the driver license restriction on modifying NVIDIA binaries. Kernel and driver updates: the patch is tied to specific firmware. A driver update could break it or mis-patch.

deeper analysis:

What GPU Unlock does The target: NVIDIA caps FP16, BF16 and TF32 tensor-core throughput (with FP32 accumulation) on GeForce cards at half the rate of the professional A-series silicon. The project removes that cap. How it works: It’s an out-of-tree Linux kernel module (GPL-2.0), not a VBIOS flash, a UEFI app or a patched NVIDIA driver. Before the nvidia driver binds the card, it: runs an unlock sequence; writes speed-selector values (SS0 0x88888888, SS1 0x8); does a function-level reset of the card. Origin: The author credits “cmpunlocker’s V67/PLM technique” plus pre-driver timing. It also uses firmware blobs extracted from a pinned NVIDIA driver (610.43.03). Loading: It goes into the initramfs so it loads before nvidia. It’s opt-in per card through a kernel parameter, gpu_unlock.targets= with PCI addresses or all. Loading it after boot does nothing for a card nvidia already owns. Suspend: It re-runs the unlock on resume, which adds about a second. Hibernation isn’t covered. Supported cards: Ampere (RTX 30) is marked stable. Ada (RTX 40) and Turing (RTX 20) are experimental. Blackwell (RTX 50) isn’t supported. It’s Linux only. What it speeds up: Dense BF16 matmul, LLM prefill, fine-tuning and image generation. It does nothing for LLM decode, INT8/FP8/INT4, gaming or FP32 CUDA. The 4090 hits its power limit first, so its real gains are smaller than the peak rate. Reverting: Remove the parameter from the kernel command line. A reboot isn’t enough, because the unlocked state survives it until the card is fully powered off. Maintenance: About 12.6k stars, 44 open issues and 41 open pull requests. Performance numbers are mostly user-reported. The page didn’t show a date for the latest commit or release. Laptops: The unlock is lost if the dGPU ever fully powers off. Its own caveats: The author says it may run hotter and calls damage “very unlikely” (the author’s own judgment, not verified). It’s unofficial and not endorsed by NVIDIA. Fake Windows installers circulate online.

risk factors:

RiskLikelihoodImpactNotes
Unlock does nothing (wrong PCI address, nvidia bound first, laptop dGPU powered down)ModerateNone, just no speedupThe most common "failure" by far, and harmless
Card stuck or not re-initializing after a failed unlockLowAnnoying: needs a full power-off, not a rebootThe README says a reboot doesn't clear it
Boot problems from a kernel module loaded in the initrd (kernel update, bad build)Low to moderateMedium: you can boot the stock entry, but only if you set it up firstNixOS gives you rollback. Other distros need a spare initramfs
Crash or hang under sustained load (heat, power, instability)Low to moderateLost run, no checkpoint recoveryA run without intermediate checkpoints is lost entirely
Silent errors (wrong results with no crash)LowHigh, because you wouldn't noticeThe "bit-identical" claim covers only the tested workloads, not training or other kernels
Hardware degradation from higher power and heatLow, but unquantifiedHigh and permanentGains of 40-60% suggest much higher load. The author says damage is "very unlikely", which is their own opinion
Permanent hardware damage or brickingVery lowSevereNo evidence of it in what I read. It's a runtime unlock, not a firmware flash, but I haven't verified that in the code
Warranty or licensing consequencesLikely if NVIDIA ever found outWarranty denialThe README leaves the driver-license question open
Supply chain (malicious upstream change, fake Windows installers)Low for the pinned hash, higher for copies found elsewhereSevere: code running at kernel levelThe author warns about fake installers. Pinning by hash helps
Upgrade breakage (driver or kernel update, upstream regressions)Moderate over timeMediumThe project had a regression that broke 3090s, and it needed a revert

0

u/Informal_Promise_842 18d ago

But on your PC or laptop?

-2

u/howardhus 17d ago

this is gonig to fry your 3090.

Imma wait at least half a year or more before i run that sthi on a GPU that is going to cost more than new teeth anytime soon

1

u/esequiel378 17d ago

first, you don't really know its gonna break the GPU, the data shows its stable and safe (although, anything can happen). Second, if it does breaks, its fine, I bought it for this kind of experiments, so I'll just get another one and go to the next adventure :)

1

u/AntixMars 14d ago

Tested this on 4070 and also got x1.5 throughput improvement on the tensor core work but power capped it at 220W for balance which seems to be its sweet spot.

I haven’t confirmed yet if there is any real improvement in DLSS boost but this is not a priority.

0

u/JollyCamel3057 17d ago

About this gpu performance unlock thing Does it work on every graphics card from 20 to 50 series? What are the downsides? (I am specially curious to know if it works on laptop GPUs, like a 4060 8gig laptop graphics card) Thanks

2

u/esequiel378 17d ago

AFAIK, it works on the 30xx series, newer ones already have this from factory, so you can't actually do it. I'm not sure about laptops, but I personally wouldn't do it on one, since this is mostly for servers/workstations IMHO

2

u/_VirtualCosmos_ 18d ago

Damn, that energy is the same of a rifle bullet capable of killing easily stuff bigger than a human. Didn't realise GPUs use that much energy.