On Mon, 2005-12-12 at 03:06 +0100, Herbert Poetzl wrote: > On Sun, Dec 11, 2005 at 10:28:04PM +0200, Roché Compaan wrote: > > On Sun, 2005-12-11 at 11:34 -0800, Alexander Kabanov wrote: > > > hi, > > > > > > i'm having similar errors (I do have limits and scheduler set, using > > > rlimits (as, rss, nproc) and scheduler) whenever i do stress testing, > > > (overloading mta or web server for example). > > > > > > during a stress test, some applications die because of no memory > > > available or can't fork, some stop with segmentation fault (not able > > > to do vserver <vs> enter),. when attacking httpd might have httpd > > > <defunct>. > > > > I am experiencing the same problems. The segfaults and not being able to > > enter a vserver from the host *really* worries me. > > well, if the limits are reached, the guest can not create > new processes and/or instantiate more memory ... of course > this might lead to program termination and the fact that > a guest cannot be entered (as the limits are hard limits). > raising them will make it all work again ...
If the vserver is hitting the limit then I'm less worried because I can solve the problem by increasing the limit. I misread and thought that there was plenty of memory to spare. Would I be right in assuming that increasing only the virtual memory will solve the problem? I don't mind if virtual servers use swap space if they need memory because we have plenty of disk space, but I don't want them to consume all the physical memory on the box. Does setting a hard limit for RSS achieve this? -- Roché Compaan Upfront Systems http://www.upfrontsystems.co.za _______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
