Memory Usage Sdk Browser vs Samples
Hello,
I noticed that the SDK Browser that is included with the SKD only allocated 72mb of ram, and if left running - goes down to 7mb of ram. Very impressive. However, when running the hello world sample in release mode, I get ~122mb of ram allocated. I get similar allocations on the app I'm working on. My memory provider marks the allocations as unresolved so I'm not sure what its from. Any ideas?
I noticed that the SDK Browser that is included with the SKD only allocated 72mb of ram, and if left running - goes down to 7mb of ram. Very impressive. However, when running the hello world sample in release mode, I get ~122mb of ram allocated. I get similar allocations on the app I'm working on. My memory provider marks the allocations as unresolved so I'm not sure what its from. Any ideas?
Re: Memory Usage Sdk Browser vs Samples
Could you please indicate how you are measuring the allocated memory?
Re: Memory Usage Sdk Browser vs Samples
I'm using both Visual Studio's diagnostic tools and also running in release with no ide attached, using task manager.
Re: Memory Usage Sdk Browser vs Samples
The SDK Browser binary included in the SDK uses D3D11, while our samples utilize D3D12. This difference could explain the memory variation you’re observing.
All our samples display memory usage in the Stats panel (accessible via CTRL + F). Please note that this reflects memory allocated by Noesis and does not include contributions from third-party libraries, drivers, the operating system, etc.
All our samples display memory usage in the Stats panel (accessible via CTRL + F). Please note that this reflects memory allocated by Noesis and does not include contributions from third-party libraries, drivers, the operating system, etc.
Who is online
Users browsing this forum: No registered users and 5 guests