1 intensive days test
By KillerBoy | October 1st, 2007 | 9:25 am
I’ve tested for a standard work’s day (whitout xp virtual memory) and my laptop crash 2 times for insufficient memory (I’ve 1GB RAM and I’ve set 1600 mb cache) while running my standard applications (VC# Expres, VWD Express, SQL Server 2000, Outlook 2003, Programmer’s Notepad, WinVi32, uTorrent, Abilon, some others).
Oct 01, 2007
whitout xp virtual memory
Thats ur problem. eboostr is not a replacement for virtual memory i believe.
Oct 01, 2007
Yes, Louie, thank you. KillerBoy you should not disable your virtual memory, eBoostr is not a replacement of it.
Oct 01, 2007
what does xp vm?
store in a cache on hdd the recently used files in current session for quickly access when re-need
what does eboostr?
store in a cache on hdd and/or removable media some accessed file and refresh it when needed
using a removable for quickly access to cache and not access on disk
If the vm isn’t touched where is the gain?
Only for frequetly accessed file? If so what is the gain against a correct combining of defragmentation and the prefetch system? (if the hdd isn’t very very slow)
So I understand why I haven’t seen some improvement on using it.
Excuse me but… in vista the files are accessed directly from removable media without inserting that in the virtual memory if they are founded in cache
I’ve seen that with vm configured nothing is written on the cache so nothing is accessed from sd so performace aren’t improovement
I’ve seen that without vm the cache was filled from the accessed data so I’ve hope that data are quickly accessed from cache without using (for that files) the vm
If data however are written in the vm the system is, imho, unuseful because the gain of reading from sd is vanished from the writing time in the vm epecially if you reduce the amount of vm (yes, I’m exagerating to remove it at all but isn’t fully filled)
Oct 01, 2007
Windows page file (virtual memory) is used for extension of physical memory. All data which not used for some time goes directly to page file.
eBooster and ReadyBoost are not a replacement of a page file. It’s just a tool for fast reading of frequently used data. Fonts, ini files, system dlls are read by the system at every application start/load.
As you know, hard disk drives are not very good at small files random reading. For some hard drives the speed is just 1-2 MB per second. Flash memory does not have this limitation. Modern USB drives are 10-20 times faster for this operation.
Oct 01, 2007
Well. Let me explain a little.
Windows XP Virtual memory is designed to allow programs to use more memory than actually installed. Each program can allocate memory for their use. If total amount of memory exceeds real one, part of this memory (actually data) will be swapped to HDD for later retrieval. So if you have many programs running (each of them would like to use some memory for processing) you definitely need Virtual memory mechanism.
There is another story connected with program startup. To start a program, Windows program loader has to read program code from disk for the first time. Actually, data goes to system cache (also located in Virtual memory) after loading. But if programs need more memory, this cache part will be discarded and system will read program code from disk again.
Modern HDD is rather fast, but to load many program modules hdd has to move heads frequently. This process is rather slow. Flash memory can do this much faster.
So the key feature of eBoostr is to direct program LOADER to faster device, but not to replace Virtual memory mechanism
Oct 01, 2007
Ths for the tech explanation mikei, I was going to ask a similar question.