From owner-freebsd-hackers Wed Sep 10 23:45:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA02483 for hackers-outgoing; Wed, 10 Sep 1997 23:45:06 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA02478 for ; Wed, 10 Sep 1997 23:45:02 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x92v8-0000gx-00; Wed, 10 Sep 1997 23:40:06 -0700 Date: Wed, 10 Sep 1997 23:40:05 -0700 (PDT) From: Tom To: spork cc: hackers@freebsd.org Subject: Re: mmap and INN In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Sep 1997, spork wrote: > I've attached two messages I dug up out of the mail archives that seem to > contradict each other. Gary says mmap + INN is a good thing, and Mike > says it's a bad thing... > > Who should I listen to? We're close to going live with a 2.2-stable news > machine, and I'm a bit confused about what INN optimizations to go with. > > Thanks, > > Charles mmap() was never really broken, INN just had some assumptions on how it ought to work. Make sure you use MMAP_SYNC. I also have the nnrpd's mmap the active file too (this is not part of stock INN 1.5.1). I have seen corruption in the active file, but only after a crash. I basically saw a bunch of zeros added near the end of the file. If innd doesn't die, I don't have a problem. I don't thing the INN port config.data defaults are the greatest. The BLOCK_BACKOFF setting is too high (should be as low as possible, since basically everyone uses channel feeds, and they will clear quickly), and ICD_SYNC_COUNT is too low and will mean that you will sync almost every second. Also, NNTP_ACTIVITY_SYNC is too low, among other things. Tom