Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!newsfeed.internetmci.com!in2.uu.net!van-bc!uniserve!usenet From: tom@uniserve.com (Tom Samplonius) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: INND1.4+MMAP=BROKEN MESS Date: 10 Nov 1995 19:28:55 GMT Organization: UNIServe Online Lines: 25 Distribution: world Message-ID: <48095n$es4@atlas.uniserve.com> References: <46ldvj$l3c@buffnet2.buffnet.net> <imzqekgzmt.fsf@hidden.cs.uidaho.edu> <472u66$dpo@blackbush.xlink.net> <47f3gf$2gu@atlas.uniserve.com> <47m335$eu3@buffnet2.buffnet.net> <47m8kq$gqq@atlas.uniserve.com> <47qcfu$4r8@buffnet2.buffnet.net> NNTP-Posting-Host: pc.sdf.com Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Newsreader: WinVN 0.99.6 In article <47qcfu$4r8@buffnet2.buffnet.net>, shovey@buffnet.net says... . > >: A bug was found a couple of days ago, in the msync code. It is quite >: likely the cause of the failed active file updates that happen with mmap >: under innd. A partial fix is in -current. > >: For now, just run innd without mmap. On a FreeBSD system there is almost >: no performance difference between read/write and mmap anyway (due to unified >: disk cache and VM system). > >: Tom > >Im told by other admins that MMAP doesnt work with BSDI either - and I >did note that I wasnt experiencing the performance penalties that my >peers said I would without MMAP (they said INN slows badly if you history >file is over 20MB - mine is over 100MB). Err.. if you look at the code, mmap() is only for updating the active file. Not used for history at all. Also, 100mb history file is normal for a full feed and a 14 day history. Tom