Didn't know there were actually any
product that did this - the only I've seen that was in the same ballpark was vRamDir back in the Win9x days, but that wasn't a fixed-size ramdisk... you pointed it at a folder and then it was basically "try to keep as much as this as possible in RAM".
I'm not sure it's a good idea for a ramdisk anyway? To be able to de/allocate memory like that, it needs more complex code than "just" a ramdisk... filesystem filter driver? And when you have a ramdisk, you generally expect access to it to be instantaneous - if you use a product that does dynamic de/allocation, you risk having to page out other memory in order to satisfy an allocation request. Depending on use case it might be smarter to simply *create* a ramdisk when you need it, and dismount it afterwards?
That's just my
- interesting to hear about Primo, though