![]() ![]() ![]() If you increase the memory clock there, it applies just fine to regular 3D loads like Heaven, but has no effect on the memory clock in P2. Regular tools like EVGA Precision, Afterburner etc. resume BOINC GPU crunching -> the card immediately switches to "P2" and the memory clock speed drops launch a benchmark like Heaven in windowed mode, halt BOINC GPU computations -> "P0" and full memory clocks are reported Inspector also shows the performance state. However, tools like GPU-Z and nVidia Inspector show the clock speed being lower. This speed is also what's reported by the Einstein and GPU-Grid apps. Running regular 3D loads the card switches into "P0" and runs the memory at 1.75 / 3.5 / 7.0 GHz. This is difficult, because at first glance everything seem OK. I expect GTX980 with more shaders to feed to be affected even more, and Einstein with generally higher bandwidth demand to be affected even more. This is meant for some less-demanding load and limits GPU memory clocks to 1.5 / 3.0 / 6.0 GHz on GM204 cards, depending on how you want to count DDR clock speeds.Īt GPU-Grid the memory controller load is ~50% with my GTX970, while loads >30% are known to reduce performance measureably. I have also seen it reported from the Bitcoin guys, but am not aware of any solution yet.Īs soon as a CUDA or OpenCL task is started, the card is limited to "P2" as the highest performance state. I stumbled upon a problem with my Galax GTX970 running GPU-Grid, which seems to affect all cards and all GP-GPU crunching, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |