3 ms·
It kinda varies if you go the GPUMMU or the IOMMU paths, but under WDDM it seems that assets can end up being on disk. https://blogs.msdn.microsoft.com/greg_sc
by dogma1138 10y ago
It kinda varies if you go the GPUMMU or the IOMMU paths, but under WDDM it seems that assets can end up being on disk.
https://blogs.msdn.microsoft.com/greg_schechter/2006/04/02/the-role-of-the-windows-display-driver-model-in-the-dwm/ https://blogs.msdn.microsoft.com/greg_schechter/2006/04/02/t...
"In the event that video memory allocation is required, and both video memory and system memory are full, the WDDM and the overall virtual memory system will then turn to disk for video memory surfaces. This is an extremely unusual case, and the performance would suffer dearly in that case, but the point is that the system is sufficiently robust to allow this to occur and for the application to reliably continue."
The only issue here is that as far as i can understand you can't really choose how this is done very specifically.
When you allocate memory the driver pretty much takes over, if you want granular over memory allocation you pretty much have to go through the GPUMMU path which means each process has a separate GPU and CPU address space so while you can control what you store in GPU memory and what you store in System memory I still don't see a way to control mapping an asset to disk specifically other than it being an edge case of you running out of system memory which results in the page file being used.