Disabling P2 on 5x1080ti (3 diff brands) nets me 1-2% increase in hashrate at expense of 2-3% power usage - not worth for me, especially that it matters mostly in memory intensive algorithms which, as all we know, 1080ti are lackluster with.
P0 it's a question of stability when working close to max. P2 will crash when miner exit, P0 won't.
Hello, this is my first post however I follow this forum from a while (and thanks for your shared experience
). So please be patient if I share too obvious things.
I investigated the P states a bit earlier so let me share my experience. When you start or stop your miner then the GPU jumps to P0 for a second otherwise it runs in P2 during mining.
The P2 state has lower frequency settings than P0. When you OC your card then you set offsets. When you start/stop then the GPU switches to P0 and the same offset is applied to the higher base frequency. This leads to crash as it is too much to the card.
I have Asus 1080Ti Strix OC cards and EVGA 1080 (not Ti) FTW2 cards. With these cards I saw that the base core frequency is the same for P0/P2 but the memory is reduced to 5 GHz on the Asus and 4.5 Ghz on the EVGA. When I overclock the 1080Ti with +500 mem then it reaches the operation frequency (5.5 Ghz -> effectively 11 Ghz due to dual rate). So the OC sets the factory maximum in P2.
You can check the absolute frequencies in Afterburner on Windows and with nvidia-smi on linux. The base frequencies mapped to the P states are burnt in so we cannot change them.
The crash happens during the short P0 period when the GPU raises the memory frequency to the factory max, 5.5 GHz and it gets the OC offset as well which results 6 GHz which is too much to the GPU.
Here you can read more:
https://devtalk.nvidia.com/default/topic/1010856/linux/how-to-force-performance-level-3-driver-381-22-with-gtx-1080-ti-/3Nevertheless let me ask you how can you fix to the P0 (or any other) state on Pascal GPUs? I have both Windows and Linux machines so I'm interested in both OS.