To save disk space with ram caching, why not just create a database of files that are to be loaded into the ram cache vs. actually having a store on the actual hard drive.
To save disk space with ram caching, why not just create a database of files that are to be loaded into the ram cache vs. actually having a store on the actual hard drive.
This storage is used to save cache contents on reboots (like hibernation file). In your case eBoostr will have to build RAM cache on each boot.
well sequential reading is quicker than random reads. I was just thinking if the Ram has to rebuild it's cache by reading either way, why not save the disk space? I was actually thinking on saving disk reading (hence boot startup time) by putting the cache on a flash drive for building from, but oddly I couldn't choose a flash drive to put the cache contents onto.
You must log in to post.