A 7-minute 1080p video that used to render in 1 minute 40 seconds now takes about 10 minutes.
Same laptop, same footage, same export settings.
The only change was a graphics driver.
Two reports landed within days of each other this week, both pointing at Qualcomm's Adreno driver 32.0.181.0.
One came from a Reddit user on a Zenbook A16 running Premiere Pro.
The other came from u/NonVeganLasVegan on a Surface Laptop 8th Edition with the Adreno X2-85, running llama.cpp over the OpenCL backend.
The second report is the one to read closely if you run models locally.
Going from driver 32.0.172.2 to 32.0.181.0 cost 69 to 87 percent of throughput.
Qwen3-0.6B fell from 98.1 to 12.8 tokens per second.
Qwen3-4B went from 29.5 to 9.0.
Qwen3-Coder-30B-A3B dropped from 26.8 to 5.9.
The poster states the laptop, software, models and operating system stayed the same, and the system was plugged in.
Nothing in that stack was broken by the model.
The floor moved under it.
This is a cost local AI rarely gets budgeted for.
You buy the hardware and tune the stack, but the pipeline still runs through a GPU driver that ships when someone else decides.
A regression arrives in a routine update and the work you did in September is gone by Tuesday.
Rented compute splits those layers apart.
Your runtime stays on the version you tested while driver churn happens somewhere you never touch.
RTX 3090 from $0.15/hr, and Buy Now Pay Later gives you zero upfront with payment after one month.
What is the worst performance regression a driver update has cost you?
https://ai.bhkcloud.com/?utm_source=linkedin&utm_medium=social&utm_campaign=bhk_social_2026w44&utm_content=evening
Originally posted on linkedin_personal