I used to have OOM killer problems with Tomcat, Apache's JSP server, but
not any more. A new variable appeared in the config settings which had
to do with the maximum memory that Tomcat would use for itself, and I
think that may have been what fixed the problem. Does Postgresql need
something like that? It may be comparing apples and oranges because
Java is very funny about the way it uses memory. It pretty much never
lets go of memory until it decides to invoke its trash collector which
if you decide to do just when the system tells you it's low on memory
can cause big problems.
Richard Troy wrote:
On Wed, 31 Jan 2007, Jeff Davis wrote:
I know this is off-topic for this list, but is there a place I can get
some details about linux OOM killer, and the conditions that cause this
OS hang when you turn off the OOM killer? I'd like to really know what's
happening, and also know more about the OS hanging condition that you're
talking about. I'd also like to know how safe the "safe" settings really
are ( vm.overcommmit_memory=2 and vm.oom-kill=0? ).
Right now I'm using FreeBSD (in a large part due to the Linux OOM
killer), but I have a different set of problems on FreeBSD.
Regards,
Jeff Davis
...Back in, oh, October perhaps it was, I did some research on this subjet
and posted my findings on one of the PG lists, so you can look into the PG
archives for OOM and my name and likely find a summary and some URLs to
more complete information.
Richard
