Saturday, October 3, 2009

Windows System Resource Manager

does this have any benifit using it locally to control apps or is this good only for "server" apps. I would love to use this to contain photoshop and its nasty leakage as well as other apps like IE. Can this work locally?

I will post some wiki info right here to get everyone the gist of it:

"Windows System Resource Manager (WSRM) is a component of Microsoft's Windows Server 2008 operating systems that provides resource management and enables the allocation of resources, including processor and memory resources, among multiple applications based on business priorities. It is also available as a downloadable add-on for Windows Server 2003 Enterprise and Datacenter editions.

WSRM enables users to manage CPU and memory utilization on a per process basis. An administrator sets targets for the amount of hardware resources that running applications or users are allowed to consume. It can allocate resources among multiple applications on a server according to defined policies.

This can be helpful in a corporate environment when, for example, your well-behaved application software has to co-exist with an application that has a memory leak. Without protection such as afforded by WSRM, your application will run more slowly and/or crash, because the misbehaving application will eventually cause problems that affect every application that shares its memory space. Thanks to the WSRM, a software application can be limited to an isolated subset of hardware resources. As a result of this, the bad effects caused by the memory leak will be limited to that subset. Hardware partitioning can also solve the problem, but it is a far more complex solution."

Here's my experince with it!
I tried this and applied it to IE8 and now I got instant bloat control! If one tab uses over 500MB of commit charge (paging file only usage amount) then it will shut down that tab and then IE8 auto recovers it! That utility is awesome! it also helps reduce thrashing by doing this.

keep track of commit charge by enabling it in task manager. go to view columns enable the commit size one! if you notice this going up in a process kill it! This will help remedy the thrashing problems. I did this and my system is so sexy smooth now! LOLz.

this is a must install for those running server 2008 and do not have very much ram and/or multitask tons like I do. ;)

also doing this tells you that most websites are the source of the bloat rather then the browser or the OS! Please keep this in mind webmasters out there. You opened the code now close it and be polite. we don't want to have to resort to above methods to deal with you! MS provides the code on technet/msdn if you look hard enough! Most webmasters forget that when they code a site they are coding a mini application so the same rules apply. make the responsibly! you still have to close the memory like a normal .exe application! do this and people (and compies) will be much happier!

Oh BTW on youtube I watch 5 videos and the process on WSRM kicks in and kills it! this is just in one tab alone! The ram usage is 320MB and the commit charge is a staggering 500MB+!!!!! ADOBE NEEDS TO SHAPE UP AND GET FLASH TO NOT BE SO BLOATED!!!!

this is my usage when running IE8 with 25 tabs inclusing Bing maps and Google street view after watching 8 youtube vids:

No comments:

Post a Comment