Results 1 to 5 of 5

Thread: Cache won't release in Windows 7 when needed

  1. #1
    Join Date
    Oct 2010
    Posts
    163

    Cache won't release in Windows 7 when needed

    I am running Windows 7 on my desktop PC. There is some misconception which I want to figure out. I have noticed that the Windows7 normally doesn’t use the entire physical RAM available for applications. My system’s current memory capacity is 4GB and I think it rarely uses over 3GB of RAM even though much more as been assigned. So anybody have idea about why the Win7 is prioritizing cache so high? Is there any reason or way to change the behavior?

  2. #2
    Join Date
    Feb 2010
    Posts
    471

    Re: Cache won't release in Windows 7 when needed

    There is simple reason and the simple answer for this issue. I think the wrong what you have made is doing a lot of assumptions or assignment without any data or real backing. As I know that the software giant Microsoft has done lot testing over it to optimize the algorithms used for caching, prefetching and paging like that. As far as think they have done their best than you ever thought about it.

  3. #3
    Join Date
    Feb 2010
    Posts
    538

    Re: Cache won't release in Windows 7 when needed

    As I gone through your problem I found that the indolence you are experiencing is due to the reality that you only have 4 GB of RAM. As I know Windows 7 is optimized better and may run better only if you give it more than 4 GB. You may think that the cashed RAM as an available RAM. . That is because the memory that has been used as cache is frequently obtainable to be cleared for application use. If the System’s memory was totally used up with no more memory existing for increasing memory necessities, then your computer would be even slower than you are presently experiencing.

  4. #4
    Join Date
    Feb 2010
    Posts
    570

    Re: Cache won't release in Windows 7 when needed

    I think that this kind of issue is not being happening at all. It doesn’t need to happen like that. For additional information check RAM map by systeminternals. As I know the application page file in Windows 7 is not there for use when physical memory is full. The OS uses physical memory to write down pages that are established to be stationary. You should use perfmon to check the page faults only if you are worry about the system using page file.

  5. #5
    Join Date
    Feb 2010
    Posts
    589

    Re: Cache won't release in Windows 7 when needed

    How can you say that you are lacking in memory and suffering performance issued? There are nearly 120 processes running on your system. Windows is also using your page file pretty seriously. It's doing its best thing it can to page out data that's not being used yet by keeping the majority active applications in memory, but it also keeps some few hundred Megabytes accessible cached for anything else you open. It does like this when you have a set of stuff running, there's always a little more existing. It's fairly implausible how well Windows 7 manages memory to get you the good number performance. If you think SuperFetch and Windows 7 itself are not doing the job then go ahead and disable the page file and turn off Superfetch .

Similar Threads

  1. Replies: 6
    Last Post: 12-09-2011, 11:05 PM
  2. Cache settings (intensive cache usage)
    By Valliy in forum Technology & Internet
    Replies: 7
    Last Post: 02-07-2010, 07:13 AM
  3. What are the Windows Cache Extension for PHP?
    By Flaco in forum Software Development
    Replies: 5
    Last Post: 14-03-2010, 06:57 AM
  4. windows Xp PreFetch Cache Setup
    By jennifer in forum Operating Systems
    Replies: 3
    Last Post: 14-07-2009, 09:56 AM
  5. How can i clear the updates cache in windows
    By Orton in forum Operating Systems
    Replies: 3
    Last Post: 04-05-2009, 05:20 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,422,513.17172 seconds with 17 queries