Windows 7: HELP: Task Manager!!!!!

Tepid · 19 Mar 2010

I agree,, turning off superfetch is not going to improve anything.

CommonTater · 19 Mar 2010

Quote: Originally Posted by logicearth

The disk trashing you are referring to. This is caused by the initial loading of the system, while you are installing your various application and others. After a while when the system is no longer in such a high level of flux any disk trashing will subside. However, this disk trashing should not have an impact on the system if it is SuperFetch that is trashing the disk. Any I/O operation that SuperFetch preforms is done so at a low I/O priority, meaning it will only use I/O resources when it will not effect the performance of the system.

Actually I was more worried about the increased load on the hard disk than anything else. I've been using this for a couple of weeks now and it's still pretty busy... although (if you read my other big thread) I'm slowly getting it figured out and quieting things down... At least the main system is going into standby now.

Quote:

Second the data cached in RAM is never paged out of RAM. If an application requires the space occupied by the cache it is simply overwriting with zero overhead. There is no speed-up or getting a smoother system when you turn off SuperFetch, all you get is wasted RAM.

Windows Administration: Inside the Windows Vista Kernel: Part 2

Quote:

Whenever memory becomes free-for example, when an application exits or releases memory-SuperFetch asks the Memory Manager to fetch data and code that was recently evicted. This is done at a rate of a few pages per second with Very Low priority I/Os so that the preloading does not impact the user or other active applications.

It may not impact me or my active programs... but is it really necessary?

If it's like predictive disk caching (a la win95) I'm betting the number of misses renders it pointless.

But thanks to you and Whs for the extra info... As I said I'm still learning about Win 7, so your info does not fall on deaf ears.

niic · 22 Mar 2010

Hi all,

Thanks so much for all this useful info. Really helps.

However I'm still lost as to the 'Free' mem being very low while 'Available' very high.

If I was to load another heavy application like a CAD/3D package would I see Windows 7 crash given Free is only at 12mb? I'm still a bit confused as the Free/Available relationship.

Again, thanks to everyone who is posting in this thread. Very helpful!

Nick.

logicearth · 22 Mar 2010

Quote: Originally Posted by niic

If I was to load another heavy application like a CAD/3D package would I see Windows 7 crash given Free is only at 12mb? I'm still a bit confused as the Free/Available relationship.

No Windows 7 would not crash. Lets put it like this. Available equals Free. So forget about the independent Free value. That should make it easier.

CommonTater · 22 Mar 2010

Quote: Originally Posted by niic

Hi all,

Thanks so much for all this useful info. Really helps.

However I'm still lost as to the 'Free' mem being very low while 'Available' very high.

If I was to load another heavy application like a CAD/3D package would I see Windows 7 crash given Free is only at 12mb? I'm still a bit confused as the Free/Available relationship.

Again, thanks to everyone who is posting in this thread. Very helpful!

Nick.

Have the Resource Monitor on screen while you load an ap... you'll see the memory profile change... The cached stuff is dumped right away, to make room.

niic · 22 Mar 2010

Yeah I just dide some tests and have been watching the values. I found some good articles on it as well...

Windows Administration: Inside the Windows Vista Kernel: Part 2

The best I can understand this now is it displays physical mem that hasn't been assigned to anything.

Available = Standby (SuperFetch) + the Free
Cached = Standby + Modified

Thank you all for your info. Very helpful! cheers

Windows 7: HELP: Task Manager!!!!!

HELP: Task Manager!!!!! problems?