temp file and allocating cache error
By steve | December 7th, 2008 | 11:41 pm
eboostr (beta 473) seems unhelpful once the cache is filled 100%, and upon rebuilding cache, the allocating process takes 20 minutes and showed an initial error something like “-3434543o5494Mb”, once it’s done with the allocating, the cache building process was very slow…
also, eboostr seems to only cache certain system and application files, wouldn’t it be nice to have it cache all the temporary files as well? – just put a limit there in terms of how much space should be used for temp files and how much for sys files, otherwise, it’s not really significant in terms of reducing hard drive activities….
Dec 08, 2008
eBoostr caches any files that are frequently read. At least if you do not exclude them by location or mask.
An error size will be fixed in the next build (hope the third attempt will finally get rid of it.)
Allocating took 20 minutes? What is your cache device? Seems that it has a very low write speed.
Dec 18, 2008
hi, to follow up on my previous post about cache allocation and building speed – I use a PNY 4GB usb drive and it actually DOES take about at least 20 minutes to allocate and build the cache, the access speed, according to eboostr itself, is anywhere between 15-17MB, so, I assume that’s a decent speed…
But that’s not my major concern, the REAL issue is, when I first used eboostr, it fills less than 50% of the 3.8GB cache, but now, even if I remove then rebuild the cache file, it always fills up 100% of the cache upon allocation and building, so, why is that? — does that mean it no longer cache new files, or, every time it needs to cache new files, it has to spit out some old files first? and my primary purpose of using eboostr is to reduce hard drive access since I’ve had three hard drive failures in the past, so, can anyone give an honest assessment of eboostr’s effectiveness in reducing hard drive activity? thanks very much! – user from new york.