Hi Chandra, > On Tue, Apr 19, 2005 at 04:48:38PM -0400, Marc E. Fiuczynski wrote: > > Hi Chandra, > > > > The following program will be killed in our system by the > > memory controller (both the E17 based one and a prior one): > > > > dd bs=4096 count=250000 < /dev/zero > /bigfile > > > > The class within which this command executes is setup as follows: > > > > res=mem,guarantee=-2,limit=125000,total_guarantee=100,max_limit=100 > > > > The default class has the following: > > > > res=mem,guarantee=-2,limit=-2,total_guarantee=322735,max_limit=322735 > > That is bad behavior.... > > Have you played with the config parameters to see if it helps ?
I've set fail_over=2000 to avoid having the memory controller kill a process. Now I need to tune the other config parameters to compensate for the lack of an I/O controller. In some sense I want to let classes oversubscribe and only when overall memory pressure increases force them to be squeezed back into their memlimit. My thought is to use shrink_at=200 and shrink_to=90. What are your thoughts? Marc ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
