Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Possible Duplicate:
Windows 7 memory usage

enter image description here

Hi,

I'm using windows 2008 server 64 bit OS, I've uploaded the snap shot of my task manager when minimum processes running

It shows Total memory 8190 MB Cached memory 4315 MB Free 3402 MB

So effectively I get only 3402 MB of total RAM usage My question here is more than half is used for cached memory is there any means I can decrease this cached memory, in turn I can increase my free memory. I need to do this because my Application requires at least 5GB RAM and it crashed when run in this system. Please give me a solution for this

Thanks in advance

share|improve this question

marked as duplicate by Mokubai, Tom Wijsman, Sathya Jun 30 '11 at 15:36

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

1  
Crossposting does not impress. –  Ignacio Vazquez-Abrams Jun 30 '11 at 4:26
    
Not to nitpick or anything, but I don't remember there being a windows 2007 server... Anyways, have you tried upping the Virtual Memory? –  imtheman Jun 30 '11 at 4:52

1 Answer 1

Windows does this automatically. As soon as programs request more memory, the MM module reclaims the cached memory.

Edit: I was wrong. They actually implemented this back in Vista.

http://technet.microsoft.com/en-us/magazine/2007.03.vistakernel.aspx

share|improve this answer
    
Is this feature available in other windows? –  Greenhorn Jun 30 '11 at 13:43
    
When my application crashed Cached memory was around 4 GB and free memory was ZERO –  Greenhorn Jun 30 '11 at 13:46
    
@Athreya Free memory being at (or near) zero is good, it means that it is actually being used for something and likely has nothing to do with your application crashing. As surfasb stated "cached" memory is released as and when the system needs it as it is simply caching data that is read from the disk. Think of "cached" as "being used but actually available for programs" memory. –  Mokubai Jun 30 '11 at 15:22
    
Crashing an application has really nothing to do with free memory. Depending on the application and how it is written, applications can get unstable at even 1.5GB. This is due to the atrociously resource intensive nature of pulling data out of memory as compared to just fetching things out of cache. Another thing is the application could of crashed due to other reasons. Just because it asks the operating system for that much memory, doesn't mean it is using it all (ask the C++ guys. This is what they constantly bash on new programmers about). –  surfasb Jul 1 '11 at 0:20
    
More than likely, a program is consuming that much memory because of an internal error and parts of it are terminating early without releasing it's resources. –  surfasb Jul 1 '11 at 0:22

Not the answer you're looking for? Browse other questions tagged or ask your own question.