[Jelc]

Ajde, kaj jambrate-na nekim nvidia grafama su driveri znali natjerat grafu na 40% opterećenja kad su bila uključena dva monitora

Ovo je jedna od stvari na koje sam naletio:

I had someone ask a similar question back in November about the 58xx series and how they too run at a higher performance state with multiple monitors plugged in. As far as I know the GTX 480 series is affected by the same issues the 58xx series is, so the technical explanation is the same. So here's that response:

"If you recall our 5800 series article, we mentioned that AMD finally has the ability to change the clock speeds on GDDR5, using fast link retraining. In order to make FTR work without disrupting any images, FTR needs to be done during a v-blank period so that the monitor isn’t reading from the front buffer, as the front buffer will be momentarily unavailable during the FTR. This is very easy to accomplish when you only have 1 monitor, because there’s only 1 v-sync cycle to deal with.

The issue is that with multiple monitors, there’s no guarantee that the all of the monitors will be perfectly synchronized. It’s possible for the monitors to be out of sync (particularly when using different display types, i.e. a DVI and a DP), which results in flickering on any monitors not in sync with the monitor the FTR was timed off of. This is the flickering you see when you have an overclocked card, as the card is accidentally switching GDDR5 speeds when it shouldn’t be. [At the time, a card overclocked with CCC would not go in to the correct 2-monitor PP idle state]

So the reason AMD keeps cards at a higher state when multiple monitors are attached is to preventing that flickering. This means at a minimum keeping the GDDR5 at whatever it defaults to (1000mhz/1200mhz). I’m not entirely sure why the GPU is kept at a higher state too, but my best guess is that there may be performance issues with trying to draw to 2 large monitors at such low clock speeds. Or it may be that this is just easier than creating another powerplay state. "

Ultimately there is no "fix" because this is not a bug. If anything it's a limitation of TDMS technology. I believe the FTR issue can be fixed with DisplayPort since it uses 1 shared clock, but I don't have a pair of DP monitors on hand to test that right now.