On Wed, Jan 11, 2006 at 09:58:43PM -0800, Robin Lee Powell wrote:
> On Thu, Jan 12, 2006 at 03:38:25AM +0100, Herbert Poetzl wrote:
> > On Wed, Jan 11, 2006 at 04:38:58PM -0800, Robin Lee Powell wrote:
> > > I want my VServer to not be able to choke my real server by
> > > using up all the RAM, so I set an RSS limitation.  As you can
> > > see, it's not working very well:
> > > 
> > > PROC:           72             142              -1           0
> > > VM:         104883          223551              -1           0
> > > VML:             0               0              -1           0
> > > RSS:         56597          131072          131072         356
> > 
> > well, as we see it is working very well ...
> 
> Well, in some sense.  I don't want my processes to get killed.
> 
> > > The problem I'm having is that instead of swapping things out,
> > > processes simply get killed, even when there's lots of swap
> > > left.
> > 
> > as I explained many times (here and on IRC) you do not really want
> > a swap-out behaviour, but once again here is a simple example ...
> > 
> > just consider 10 guests, 
> 
> I have exactly 1, and will only over have 1, so this simply doesn't
> apply.  I really *do* want swap-out behaviour.

for one guest, why do you care about limiting memory at all?

I mean, why not 'just' let it use up what it takes?

> > > So, I'm wondering:
> > > 
> > > What do RSS and AS actually *mean* when applied to the whole
> > > VServer?
> > 
> > RSS means Resident Set Size (i.e. the amount of memory which is
> > actually 'present' in RAM), and AS means Adress Space, which is an
> > artificial limit which 'could' be compared to swap space, but does
> > not necessarily end up in swap ...
> 
> OK, but it might?  I really do want the swap behaviour.

again, I don't see the point in limiting a setup with a 
single guest ... of course, once the real memory is
exhausted, the swap space will be used ...

> > for now, I would suggest to do what you actually said, and use the
> > RSS hard limit for preventing customers from using up all your
> > memory ... (i.e. make it large enough so that it doesn't hurt the
> > friendly customer, but small enough, so that your system will keep
> > running when somebody is excessive)
> 
> OK.  That's really too bad, as it doesn't help my needs very much,
> but if that's the option, then there you are.

maybe you could describe your needs and/or the entire
setup in more details, so we could get a better
impression ...

best,
Herbert

> Thanks for all your help!
> 
> -Robin
> 
> -- 
> http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
> Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
> Proud Supporter of the Singularity Institute - http://singinst.org/
> _______________________________________________
> Vserver mailing list
> [email protected]
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to