From owner-freebsd-isp Thu Mar 19 19:46:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11689 for freebsd-isp-outgoing; Thu, 19 Mar 1998 19:46:35 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11634 for ; Thu, 19 Mar 1998 19:46:25 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id FAA00902; Fri, 20 Mar 1998 05:45:57 +0200 (SAT) From: John Hay Message-Id: <199803200345.FAA00902@zibbi.mikom.csir.co.za> Subject: Re: Slooow expires (inn 1.5.1 and 1.7.2.insync1.1d) In-Reply-To: from Wm Brian McCane at "Mar 19, 98 04:11:22 pm" To: root@bmccane.maxbaud.net (Wm Brian McCane) Date: Fri, 20 Mar 1998 05:45:57 +0200 (SAT) Cc: isp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > I had already thought of that, guess I should have mentioned it. The > > > makehistory has been running for over 11 hours. I notice it is spending > > > nearly ALL of its time in 'biord' according to top. This is the same > > > thing I noticed with expire. > > > > I think you just went over some limit and now the database isn't > > handled in RAM anymore but on disk. It might be not enough RAM > > or the limits in login.conf might be too low or something like > > that. Try running /usr/bin/limits out of cron the same way your > > expiry is done and have a look at its output. > > > > Inn and its utilities change automatically over from memory > > based usage to disk based usage for some of its operations > > if it can't allocate enough memory... and then performance > > sucks big time. > > > Actually, I have been running it from my command line the past few times > while testing different versions of INN. If I run limits from the > command line I get: > > Resource limits (current): > cputime infinity secs > filesize infinity kb > datasize 32768 kb > stacksize 16384 kb > coredumpsize infinity kb > memoryuse-cur 131072 kb > memorylocked-cur 32768 kb > maxprocesses 64 > openfiles-cur 256 > > Does this look sufficient? > Nope. The datasize limit is much too small. Try to make it as big as you can... at least for this run and see if it makes a difference. That is the maximum size the data of a process may be in memory. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message