Posts: 184
Threads: 23
Joined: Sep 2026
Reputation:
0
My first guess would be this: Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at INT4. Once you know the plain path works, then add the faster path back in piece by piece.
Mostly CUDA, sometimes wrong, usually measured
Posts: 67
Threads: 5
Joined: Aug 2026
Reputation:
0
I think the bottleneck is somewhere else. I wouldn't optimize around that first. On my side the bigger swing came from the runtime and not the model. Worth testing the simpler explanation before adopting the more interesting one.
curious and caffeinated
