4wd: I used to love
vramdir on win9x, it basically tried to cache as much of a folder/mountpoint in memory as possible - this worked extremely well, and wasn't a ramdisk as such. I assume ImDisk in dynamic mode still has a fixed upper limit and shows up with a drive letter? IMHO that's the worst of both worlds - you still impose a maxsize, you risk paging (if you set a maxsize that's too large), and even though you might get the disk hit penalty, you don't have persistant storage.
I would have thought you'd get a performance hit from doing that every few minutes though?-4wd
Not when you're only writing the changed parts
Sure, there's some overhead in dirty-tracking, but it works pretty well. What you get is a guarenteed max memory usage, guaranteed performance characteristics of the ramdrive, relatively-consistent behavior with performance you can reason about. It works very well for %temp% and data storage for a few applications - but I do need to do a little manual work every now and then for installers and whatnot.
The arragenment works pretty well, though. And if I need a ramdisk for temporary purposes (manipulating an ISO file or other kinds of virtual filesystem shenanigans, doing some raw manipulation on 100k web profiles, whatever) it's nice having a tool that lets me create a temporary ramdisk for that purpose, rather than having to reserve space for that all along (if ImDisk doesn't do this
very smartly, just reserving the capacity takes a bunch of memory).
