Menu
What's new
By:
Filters

Kontakt Ram Management issues inside VEP7 with 128GB Ram

midiman

midiman

Senior Member
I have a Kontakt Ram memory question for the forum that I wonder if anyone has managed to deal with. When I load my large template in Vienna Ensemble Pro, with many Kontakt Instances inside it it fills up my 128GB ram fully when it is loading Once it completes the loading process with all instances the Ram it reaches the maximum Ram of 128GB. Then after about 10 minutes of the complete loading, it starts to unload some stuff, probably based on my purge settings, or the DVD settings (I'm not sure how it manages this process exactly) and brings it down to 91GBs.

I usually purge the memory from Kontakt instances that are used less and Vienna and Kontat can preserve that information so that when I reload the template it goes back to whatever occupied Ram state it was in when I last saved the Vienna Ensemble pro template. So my question is, why Kontakt has to load ALL the sounds fully to the point of filling out the 128GB, and probably having to even use hard disk memory for the sounds that it can't fit in the 128GB capacity, and once it completes to full template loading it only then starts to proceed to purge all the Kontakt instances I were purged, and after about 10 minutes or more it brings the ram down to 91GB.

It seems to be inefficiently built. To load everything, which also takes a lot of extra time especially as it has to use more than the 128 gb available so having to use a hard disk to temporarily load all the sounds that don't fit in the 128GB ram, which is super slow since hard drives are slower than ram, to then unload from 128GB to 91Gb. It is not the most efficient programming in Kontakt when it comes to loading previously purged instruments.
Is anyone familiar with this situation? Can you advise?
Click to read more...
 
The OS is offloading RAM content to your drive (swap file) in order to make space should an app require it. Upside: Your system keeps running instead of crashing or starting to get slow, downside: should it offload the wrong things you might experience drop-outs, pops and clicks during playpack.
 
Ben said:
The OS is offloading RAM content to your drive (swap file) in order to make space should an app require it. Upside: Your system keeps running instead of crashing or starting to get slow, downside: should it offload the wrong things you might experience drop-outs, pops and clicks during playpack.
Click to expand...
I agree it is a good thing, the use of the swap file. The issue is why does Kontakt needs to load all the sounds in its fully loaded status, and only after loading everything it can start to return to the purged state it was since it was last saved. So the ending state of the template is 84Gb of ram filled, after the loading of the VEP fully completes. However, to get there, it needs to first inefficiently load the 128GBs of ram, plus whatever has to go to the swap file, before it can then start the purging process.
So the question is not regarding the Swap file, which is a great thing, but rather why can't Kontakt manage to load directly to its purged state, to whichever purged stated it was when it was last saved. The Sine player does not experience these issues, in my experience.
 
You must log in or register to reply here.
Top Bottom