Csantucci, on 24 January 2022 - 05:57 AM, said:
Hi James,
the problem is that my old computer, although Win10, does not display VRAM data (as I have already written somewhere else), even with your feature. So for me the only way to test is using external tools.
I thank you about the Video memory paging info, which was new to me.
If the committed GPU memory is even greater than a GB in my case, this indicates that the benefit of the code change is even bigger.
Carlo,
Great news and thank you for using an alternate tool. I would continue to use it and others tools like it. When the diagnostics provided do not work with your setup something has been overlooked. I am sure we are not alone in this dilemma.
So regardless of GPU paging to system ram, your test with GPU-Z proves that for the moving camera, you saw some evidence of GPU memory being managed. To stress again, this is for a MOVING camera, a camera that travels from one tile to the next. The test that I posted was for a STATIC, or fixed camera that stays on one location throughout the activity. In my post, I saw no evidence that anything was being managed, which is the same effect that you saw when "reduced memory usage" was disabled. I am wondering if you have a test setup that can mimic my test.
The following is directed at the naysayers for using external testing tools. Until a tool can be crafted that works with all currently supported O/S in OR, ignoring my results and discarding/discounting my hard work offers no proof that my methods are invalid. It is preferable to try other tools to verify that something is working than to accept on faith that is does what it claims. This is not the first time or the last that something has been coded that does not work across the board and it should be accepted that users will try to find a way around a problem. Indeed, GPU paging to system ram is proof that this external tool works very well, as it demonstrates that GPU memory is not being managed, the capped results. In OR when GPU memory is being managed then paging should not occur, which is what you saw. All it requires is a little common sense to interpret the results correctly. My graph clearly states total system + OR for both CPU memory and GPU memory. The raw data in text form clearly indicates when runactivity.exe starts and ends.
Thanks for your help Carlo and I think Serana has solved the GPU management for at least the moving camera.
Steve