Content-Type: text/plain; charset=US-ASCII
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Robin Holt <holt@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: Large memory application exhuasts buffers during write.
Date: Fri, 26 Mar 2004 12:47:10 +0200
References: <20040326012056.GB19152@lnx-holt>
In-Reply-To: <20040326012056.GB19152@lnx-holt>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <200403261247.10807.vda@port.imtp.ilyichevsk.odessa.ua>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1166
Lines: 27

On Friday 26 March 2004 03:20, Robin Holt wrote:
> We have a large memory application which is being killed by the OOM
> killer.
>
> This is a 2.4 based kernel with many of the redhat patches applied.
> Before the application is started, there is approx 350GB of memory
> free according to top.  When the app starts, it mallocs a 300GB
> buffer, initializes it, does computations into it, and then starts
> to write it to a disk file.
>
> What we see happen is the first approx 30GBs gets written and then
> swap starts getting utilized.  Once swap has been heavily utilized,
> the OOM killer kicks in and kills the job.

How many swap do you have? What do you see in top?

> The application is a vendor provided app and probably cannot be
> modified.  Does anybody have any suggestion on possible changes
> to make to the kernel to eliminate or significantly reduce the
> likelihood that the job gets terminated.
-- 
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/