Lukas from what I see it looks like swap was not being utilized. It was available but not used.
On Saturday, February 2, 2013, Lukas Tribus wrote: > > Notice that having the HAproxy box swapping is a huge performance killer > and you absolutely do not want to do that, so apart from tuning/configuring > the OOM killer you should track the issue down and avoid memory depletion > and swapping in first place. > > > > ---------------------------------------- > > Date: Sat, 2 Feb 2013 12:34:03 +0000 > > Subject: Re: haproxy invoked oom-killer > > From: [email protected] <javascript:;> > > To: [email protected] <javascript:;> > > > > On 1 February 2013 21:57, Dusty Doris <[email protected] <javascript:;>> > wrote: > > > oom-killer just killed my haproxy instance. Anyone know if there is a > way > > > to prioritize haproxy and have it get killed after something else? Or, > any > > > tuning that might help. > > > > https://www.google.co.uk/search?q=linux+exclude+proces+from+oom-killer > > > > -- > > Jonathan Matthews // Oxford, London, UK > > http://www.jpluscplusm.com/contact.html > > > >
