Oneclick-Optimization makes it suitable for novice and intermediate users yet it is also powerful and versatile enough for computer experts. Backups of settings ensure that all user modifications can be reversed with a single click. CachemanXP requires Windows 2000/2003 or XP/XP64 to run, uses minimal resources and virtually no CPU time. The help file includes a screenshot based system performance guide.

Unlike other tuneup utilities, CachemanXP runs as a system service, minimizing resource usage and tweaking Windows at system-level.

Read CachemanXP review at TechNewsWorld.

CachemanXP has NO trial period and will always work on your system, whether you decide to purchase or not.

CachemanXP will backup your system settings (so you can always revert any changes!). The Auto-Optimize feature will examine your system and tweak it for best performance. With one click of a button! From version 1.60 on Auto-Optimize tweaks also the DNS Cache for improved Network and Internet performance.

System Tweaks

CachemanXP allows you to tweak a number of system settings.

Here is an example of a system tweak:

The tweak lets you only decide when to restart your system, the updates will still be installed!
With two clicks in CachemanXP you can get rid of this dialog for ever. 

Process List functions

CachemanXP displays a list of loaded Windows processes (Applications and System Services) along with detailed information including RAM usage.

If a process consumes more than 10% CPU Time the process name is displayed in blue color, if a process consumes more than 30% of CPU Time the process name is displayed in red.

You can sort the process list by clicking on any of the column headers. You can also change the display order by drag and dropping column headers.

If you doubleclick on a process with a window. CachemanXP will bring the window to front.

The most important CachemanXP process feature is Kill Process.

What is this function for?

From time to time a Windows program can crash and become non responding. It completely stops to react to user input. In bad cases it can slow down your whole system and even stop other programs from working.

When this happens, you usually show the Task Manager and try to end it. 

Unfortunately, it does not always work. A program can crash very badly and ignore even the Task Manager. You select End Process over and over, but nothing happens.

In this case the CachemanXP Kill Process function should help you.

It will remove the selected program from memory even if it does not play along nicely and refuses to respond. Since this feature should only be used as a last resort, you will be asked whether you really want to kill the process.

What about Windows Vista?

Cacheman for Vista is the end of the Beta Test (Beta 3). It has been delayed by the release of Vista Service Pack 1 (several core modifications were required). Please stop bombarding support about it - it's coming!

How does it work?

RAM-Recovery functionality is already included in Windows. You may ask yourself why there are so many programs that offer this feature. There is no magic behind this function. Inactive or crashed programs are simply moved from your physical memory (RAM) to a space on your Hard Drive called the Paging File (=Swap File).

If Windows does recover RAM already, why bother?

As an example imagine a computer with 1024 MBytes of RAM. After booting up you have 700 MBytes free RAM left. You launch several larger applications, work with them and free RAM goes constantly down. After hours there is only 50 MBytes of free memory left. Then you start loading a data file that needs 80 MBytes of RAM. Now the Windows RAM recovery feature becomes active, programs that have not been used for a longer time are moved out to the Paging File in order to make room for 80 MBytes of data. This process consumes both CPU time and causes disk activity - it creates a slow down. Preferably you would like to work with the data immediately, not wait until Windows makes room for it. Instead your cursor becomes a hourglass and you have to wait.

What does CachemanXP differently?

CachemanXP will not wait with the recovery until your system runs completely out of RAM. You can configure at which state (below value) CachemanXP should perform the recovery process. The postpone recovery on high system activity option ensures that no recovery happens if you are working on an important task and do not want to be disturbed. CachemanXP will wait until the job is done and perform the recovery thereafter. Since the recovery happens earlier as usual your system will have enough RAM available a much longer time.

How does this CachemanXP feature differ from RAM-Recovery in other programs?

Almost all RAM-Recovery programs do more harm than good.

It makes no sense to recover memory from programs if there is still free RAM available. You computer memory SHOULD be used to the maximum extend.

Other Ram-Utilities recover very frequently (constant disk activity). Too much data gets moved to the Paging File (so when the user switches programs there are major slow downs) and often the recovery is executed at a time when the user does something important and CPU consuming, slowing down all system operations.