Started by 4EverMaAT, January 18, 2016, 06:25:28 AM
Quote from: 4EverMaAT on January 18, 2016, 06:25:28 AMIs it possible to trim or control the usage of a process' private bytes? I had a situation where an application had about 20MB in Private Working Set, but 2000+MB in the Private Bytes! I found out later this might have been the cause of not being able to login via rdp as the commit charge peak was reached (there was about 600MB free RAM, but the commit charge was apparently full).So I'd like to know if there is a way to control a process' private bytes so that no one rogue process can affect the whole system. So far I've come up with:http://stackoverflow.com/questions/192876/set-windows-process-or-user-memory-limit recommendation of Windows Job Objects, and http://blogs.technet.com/b/mrsnrub/archive/2009/12/08/windows-system-resource-manager-wsrm-does-exactly-what-it-says-on-the-tin.aspx.But I wanted to see if process lasso has a solution or any thoughts on this. Win2008R2 Sp1 64 bit, 2.5GB RAM, Quad core processor,
Quote from: edkiefer on January 18, 2016, 07:31:36 AMHi, First thing nothing you can do to fix a bad programed app from external (user point view).I am not expert on this, but AFAIK commit size per app = private bytes , have you tried watchdog setting size to trim virtual memory size no greater to a value and trim the commit memory type .Not sure that is going to fix issue but it may help a bit .
Quote from: edkiefer on January 18, 2016, 04:38:04 PMYou can trim the memory used by a process in any of those listed memory type as trigger point.Ok, example say you don't want your X app going above 100mb , you set process name accordingly, for= virtual memory, greater than= 100mb, for= 15sec , then= trim VM, working set .Best I can say is try it, it does work .
Quote from: Jeremy Collake on January 18, 2016, 08:24:30 PM.......Everything else is dependent on the application, and you can not do anything about it from the outside - e.g. certainly can't deny it virtual memory allocation requests.