2 Threads for cache build
By sirmerlin860 | January 24th, 2009 | 7:54 pm
MB:ASUS P5N32-E SLI Plus
CPU:Q6600 @ 2.4Ghz
SND:Soundmax Integrated Digital HD Audio
VID:Nvidia Geforce XFX 280 GTX XXX Edition
WIN:Vista Home Premium x64 SP2 beta 6002
HD:Seagate 250GB x2 raid (stripe)
RAM:8GB DDR2 800mhz SLI Ready (4X2GB)
34GB Eboostr 3.0.0.490: Ultra Speed 8GB, Centrios 8GB-200X, Retail Plus 32GB(16GB), ram 2GB
AVG Resident Shield Service is reading almost every file that eboostr reads (avgrsa.exe)
ebstrsvc.exe pid 1780 is using 2 threads and 0.25 average CPU during cache build. thats 0.0625% of my q6600 cpu.
total cache rebuild on my system takes about 1 hour per 8MB
seems much slower than 486. can more threads be used for caching?
Jan 25, 2009
From what I understand about the process I expect that the cache building is slow because of the many IOPS going on, the cpu has to wait ‘an eternity’ (= 99.9375% of the time in your case) for the data to be fetched before it can be written to the eBoostr cache…
At best you could add a thread per *phycisical* device that needs caching, trying to read from the same disk using many threads at once will most likely make it slower instead of speeding it up.
Jan 25, 2009
How about changing you’re antivirus? AVG lagged my system. There are other good free ones, Avira and Avast. Also, I recommend you take a look at this great deal: http://www.techsupportalert.com/content/six-months-free-avira-antivir-premium.htm
Maybe the newest beta version will fix your problem?
Jan 26, 2009
the problem with AVG is it has a real time shield like so many of the other antiviruses out there. it checks every file accessed and it does so with 12 threads. i was hoping we could speed up the process by adding more processing power to the cache build. once the first 8GB is filled the rest of the drives fill very quickly so i assume the data is copied to the other devices at the end of the first data set.
durring the process my computer reaches a blistering 10-12% processing power including AVG and all other programs. there may be a limitation with drive speed or maybe eboostr doesn’t want to steal too much focus durring this process.