Back when I submitted my results to Bill for the benchmarks, he mentioned something about Premiere (and other CUDA apps) not allowing my GPUs to keep their memory overclock. Specifically, when I OC my video cards, I not only bump the core clock speed up, but also the memory speed. Here's a quick screen shot of my 2080Ti OC in MSI Afterburner as an example:
I've added a +110 to the Core Clock, and a +801 to the Memory Clock.
Well, Bill was right. I watched Afterburner one day while I was messing around in Premiere. Sure enough, the GPU's clock kicked back down to its default. Hm.
Apparently this is a thing with the NVidia driver, and it can be changed. Obviously: do this at your own risk, etc, etc, etc. But what you're going to need is everyone's favorite NVidia hacking tool: the NVidia Inspector.
Releases · DeadManWalkingTO/NVidiaProfileInspectorDmW · GitHub
Again: use carefully and at your own risk. You can ROYALLY screw up your NVidia driver with this app if you're not careful. Fortunately all you have to do is re-install the driver to get back in gear.
Scroll down to Section 5, and look for the entry:
CUDA - Force P2 State
That should be "On" by default. Set that to "Off", and then click the "Apply Changes" checkbox in the upper right. Done.
Now if you've OC'd the memory on your NVidia GPU, CUDA apps will not kick the memory speed back to OEM.
AdChoices