Vienna Symphonic Library Forum
Forum Statistics

181,978 users have contributed to 42,198 threads and 254,643 posts.

In the past 24 hours, we have 4 new thread(s), 8 new post(s) and 45 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP 6 instances suddenly consuming far more memory

  • VEP 6 instances suddenly consuming far more memory

    N
    N

    I've recently rebuilt my template in VEP 6, and I was really pleased with how light it seemed memory-wise - 25gb. There are 8 instances - 1 Play, 1 VSL and 6 Kontakt. Play and VSL are set to lowest preload buffers, Kontakt all purged. All was well in the world.

    Yesterday I loaded it up, and the exact same template now consumes 38gb, and 42gb connected to Cubase. I've apparently changed nothing. I'm using Task Manager in W10 to assess the figures, and its a possibility I guess that its just hopelessly unreliable. I've just checked Resource Monitor, and it says 40gb for VE Pro and 44gb connected (but I didn't check with Resource Monitor back in the happy days when I believed it was a light and nimble 25gb). I've checked every instance of Kontakt to make sure things are still purged, and aside from tiny amounts they are. I've then closed every VE Pro instance one by one to see if there was one rogue instance consuming huge amounts of RAM, but the load seems to be shared pretty evenly. That said, VSL and Play are at figures I'd expect, it's possible everything is related to Kontakt. I'm on K5.6.6, VE Pro 6.0.15864. I was fiddling around with sample rates, but I've tried at both 44.1 and 48 in the very unlikely event that this had triggered something funky.

    The only other thing I know has changed is the routine Windows 10 Pro updates. Is there anything anyone can think of that might explain this memory explosion?

    i7 4960, 64gb RAM, RME Babyface
  • N
    N

    A little bump for this, thanks.
  • N
    N

    And another bump.
  • E
    E

    I'm finding that memory consumption changes, it starts out high, but whittles down quite quickly to be slightly more (often less) than Cubase, which I assume is due to unused instruments being put to the background.

    In fact I am running Propellerhead Reason as well with the odd crash but I can end VEP6 and still save my project file in Cubase.
  • N
    N

    emotive - WOW, you're absolutely right, thank you.  Over a 40 minute period, my ram use reported in Task Manager drops from 38gb to 24gb.  That's one helluva drop.  Everything appears to be working fine at the 25gb level.  I guess while template building, I never checked the RAM use until after some time, so I was always seeing the lower figure til one day I happened to check on loading and saw this apparent huge rise.

    So the obvious question - what on earth is going on here?  Using Process Monitor, I see two figures - Private Bytes at 41gb which stays pretty much constant, and the Working Set which drops from 39k to 25k over the time period.   A quick google later - https://stackoverflow.com/questions/1984186/what-is-private-bytes-virtual-bytes-working-set - and it seems that all is not good news.  Private Bytes is the figure Windows reserves that cannot be used by other apps, and that's staying constant.

    That said, other googling suggests its not quite that simple, that in fact its reserved "just in case" and other apps can in fact claim it if needed.

    Can anyone shed any light on this?  What's my real RAM use in practice?
  • N
    N

    I think I have an explanation for the memory drops - it's a Windows process called Superfetch.  As RAM begins to fill up, what Superfetch seems to do is compress some of the RAM.  Its very effective, and happens seamlessly.  That said, I'm pretty sure that saving times are affected at the very least, I'm a bit concerned it might affect performance in terms of speed and / or CPU use.