From owner-freebsd-hackers  Sat Mar  8 18:00:06 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA18478
          for hackers-outgoing; Sat, 8 Mar 1997 18:00:06 -0800 (PST)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA18390;
          Sat, 8 Mar 1997 17:59:59 -0800 (PST)
Received: from misery.sdf.com [204.244.213.33] 
	by misery.sdf.com with smtp (Exim 1.59 #1)
	id 0w3Xtm-0004Ez-00; Sat, 8 Mar 1997 17:59:42 -0800
Date: Sat, 8 Mar 1997 17:59:42 -0800 (PST)
From: Tom Samplonius <tom@sdf.com>
To: "matthew c. mead" <mmead@goof.com>
cc: isp@freebsd.org, hackers@freebsd.org
Subject: Re: freebsd as a news server?
In-Reply-To: <199703090118.UAA10981@goof.com>
Message-ID: <Pine.NEB.3.94.970308175416.16035B-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Sat, 8 Mar 1997, matthew c. mead wrote:

>     I've recently configured a 200Mhz PPro on a TYAN motherboard
> with 128M ram and 45G of ultra wide scsi drives (5 9G drives
> total) hanging off an Adaptec 3940UW.  Anyway, I initially had
> forgotten to up the per user process limit and open files limit.
> This thing's running innd.  Anyway, I started getting messages
> about too many open files and no more processes (when many users
> connected at once).  So I changed CHILD_MAX and OPEN_MAX to 1024
> each.  Since then, expire has been taking over 18 hours to run.
> It seems to have started after the reboot that changed the
> kernel.  Does anyone have any idea why this would happen?  What
> have others used for these limits to get better performance?
> Thanks in advance!

  You don't have enough disks to get really good performance.  18 hours
sounds about right for 45Gb on only 5 disks.

  I'm working on setting up a news server with a 11 disks (mostly 2 GB),
and according to my info, that barely enough.

  Also, putting AHC_TAGENABLE in your kernel may speed things up a bit
(see "man ahc"), if it doesn't crash your system.

> -matt
> 
> -- 
> Matthew C. Mead
> 
> mmead@goof.com
> http://www.goof.com/~mmead/

Tom