Where are the limits?
As great as PCAT is for measurement and data acquisition – even PCAT can’t do everything that my site does here. And that’s a good thing, otherwise I would have become obsolete almost overnight. But what works well: PCAT is an ideal solution, because it is very convenient to use, and can complement my time-consuming measurements or help to shorten many paths. For all evaluations on the previous page, this is of course cuddling in the comfort zone par excellence, since it’s only 100-ms intervals.
Detail measurements at maximum gaming load? It’s quite possible to get close to the 500 watt limit even with a GeForce RTX 3090, but that’s only in the microsecond range, where PCAT is of course no help anymore. The first graph shows 20-ms measurement intervals, but where the mean does not represent the true spikes that may actually occur.
Once we resolve such a 20-ms interval, we see the real problem behind the very fast work of NVIDIA’s Boost. Then individual, albeit very short, peaks of up to 600 watts are by no means uncommon!
By the way, the stress test causes a very interesting picture, because the length of the real load intervals is halved! Even if you reach about 410 to 430 watts once for a single millisecond, it is then an average of about 360 watts in the 4.5-ms window. Then the card completely shuts down for about 0.25 ms. It also becomes much more relaxed with the currents. This is now once again significantly lower than what just occurred during gaming with the frequent load changes.
Modern switching power supplies should not really have any difficulties with the flowing currents that graphics cards generate. I couldn’t really measure sensationally high currents on any single card or in any of a wide variety of load situations. Very high spikes of up to 440 watts with a length of about 5 milliseconds are present, no question. If you were to scale down to the nanosecond range, then peaks well over 50 amps are conceivable, but if an OCP or OPP is already triggering by then, the circuit is screwed up and you don’t have to blame the graphics cards.
The very short load peaks can be safely put aside and you should really only worry about values that are above one to two milliseconds. By the way, not only because of the possible shutdown of the power supply by a protective mechanism, but also because of the durability. The more frantically such a graphics accelerator sucks on the power supply, the faster the secondary capacitors get into the realm of care. Anyone who then ends up saving money is misguided.
Summary and conclusion
This should suffice as a short excursus for now, because I have already described the infrared measurements in detail several times. Nothing much has changed there either, so I can skip that. Everything else from today should certainly satisfy transparency and have clarified the most important issues. That’s all I want to write about it, because it was actually more than I intended to write. If something is still unclear, then there is still the forum and the linked thread.
- 1 - Low-Level-Benchmarking with FrameView
- 2 - Power Consumption in real time with NVIDIA PCAT
- 3 - igorsLAB Interpreter and Template
- 4 - FPS and Percentile, Bar Graph and Curves
- 5 - Frame Time and Variances as Bar Graph and Curve
- 6 - Power Consumption and Effiziency in Games (GPU and CPU)
- 7 - Scope Measuring, Transients, PSU Recommendation
18 Antworten
Kommentar
Lade neue Kommentare
Urgestein
Urgestein
Urgestein
1
Urgestein
Urgestein
Urgestein
Urgestein
Urgestein
1
Urgestein
Urgestein
Urgestein
Urgestein
Urgestein
Mitglied
Neuling
Neuling
Alle Kommentare lesen unter igor´sLAB Community →