hackerman1
New member
- Local time
- 12:30 PM
- Messages
- 759
hi !
from what i´ve learned, all those RAM-optimizers are just BS.
they delete the Prefetch-cache from memory which although gives you more memory, doesn´t improve the performance at all.
on the contrary, since they delete the Prefetch-cache, you actually lose performance....
the only program that really does something useful is CleanMem:
"Cleanmem is very small as it doesn't need to do much. First off Cleanmem doesn't clean the memory from the processes itself! It asks Windows to do that. When the program starts up it grabs a list of running processes. It then grabs the ID of each process and calls the Windows API EmptyWorkingSet for each processes, Cleanmem of course checks the ignore list and skips those processes. Then Windows cleans the process, and once all the processes have been cleaned Cleanmem closes itself.
Well that's the part that seems to freak some people out, if the memory is being cleaned then the process itself will suffer! the memory will be pushed to the hard drive! the world will end! And guess what they are wrong. So let me explain why. The API call only removes memory no longer being used by the process. It doesn't touch memory in use. Here is an example from a visual basic programming stand point"
more info about it: CleanMem v.1.5.0 | PcWinTech.comâ„¢
View Video Of How CleanMem Works: CleanMem V1.5 |
CleanMem works very well, i´ve used it for 2 years on XP Vista & W7.
it´s FREE, so try it....
from what i´ve learned, all those RAM-optimizers are just BS.
they delete the Prefetch-cache from memory which although gives you more memory, doesn´t improve the performance at all.
on the contrary, since they delete the Prefetch-cache, you actually lose performance....
the only program that really does something useful is CleanMem:
"Cleanmem is very small as it doesn't need to do much. First off Cleanmem doesn't clean the memory from the processes itself! It asks Windows to do that. When the program starts up it grabs a list of running processes. It then grabs the ID of each process and calls the Windows API EmptyWorkingSet for each processes, Cleanmem of course checks the ignore list and skips those processes. Then Windows cleans the process, and once all the processes have been cleaned Cleanmem closes itself.
Well that's the part that seems to freak some people out, if the memory is being cleaned then the process itself will suffer! the memory will be pushed to the hard drive! the world will end! And guess what they are wrong. So let me explain why. The API call only removes memory no longer being used by the process. It doesn't touch memory in use. Here is an example from a visual basic programming stand point"
more info about it: CleanMem v.1.5.0 | PcWinTech.comâ„¢
View Video Of How CleanMem Works: CleanMem V1.5 |
CleanMem works very well, i´ve used it for 2 years on XP Vista & W7.
it´s FREE, so try it....
Last edited:
My Computer
- Computer Manufacturer/Model Number
- Dell
- OS
- W7-Enterprise + WS-2008 (Converted to Workstation)
- CPU
- P4 2,4GHz (at 1,8GHz, "slow" RDRAM, only 400MHz FSB...)
- Motherboard
- Intel 850E
- Memory
- 2GB
- Graphics Card(s)
- NVIDIA QUADRO2 PRO 64MB
- Sound Card
- Yes
- Monitor(s) Displays
- Dell 1702FP
- Screen Resolution
- 1280x1024
- Hard Drives
- Yes
- PSU
- Yes
- Case
- Yes
- Cooling
- Yes
- Keyboard
- Yes
- Mouse
- Yes, and i also have Cats...
- Internet Speed
- University: 100 MBit/s, Home: UMTS 7,2 MBit/s
- Other Info
- W7 on a DINOSAUR: P2 with 266MHz CPU & 160MB RAM

)