This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dedup Cache and 6.0

I was pretty sure that we were told on the beta forums that 6.0 was going to be moving its dedup cache from ram to disk (the beta forums are no longer available) I remember this because the dedup cahce settings and ram usage are huge problems for our sites and customers

But it looks like 6.0 still uses RAM, can anyone tell me why this was changed or was this only related to r3 repos?

  • The DVM dedupe cache will always remain in RAM (DVM is the current repository engine).  Backup copies are stored on disk and updated every hour (by default), but it runs in RAM to ensure faster access.  

    The R3 repository (which was intended for version 6.0 but was delayed) will handle dedupe differently and will not store a dedupe cache in RAM like DVM does. At this point, that is all the information I have regarding R3.

  • Thanks Tim, I found the beta thread I was thinking of and it was concerning r3 repos. I hate this answer as its causing tons of issues across our install base but it is what it is