From owner-freebsd-hackers  Tue Jul  8 01:55:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA06387
          for hackers-outgoing; Tue, 8 Jul 1997 01:55:52 -0700 (PDT)
Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06380
          for <freebsd-hackers@freebsd.org>; Tue, 8 Jul 1997 01:55:46 -0700 (PDT)
Received: from labs.usn.blaze.net.au (local [127.0.0.1])
	by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id SAA01650;
	Tue, 8 Jul 1997 18:55:44 +1000 (EST)
Message-Id: <199707080855.SAA01650@labs.usn.blaze.net.au>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Tom Samplonius <tom@sdf.com>
Cc: freebsd-hackers@freebsd.org
Subject: Re: Why news expiration is sooo slowww with 2.2.x. 
In-reply-to: Your message of "Sun, 06 Jul 1997 22:09:43 MST."
             <Pine.BSF.3.95q.970706220412.14775B-100000@misery.sdf.com> 
X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P<Wc^}f75I|456ez/M
 E3OlD+ZL@c>#N+Ec~Z&@;'LL!;3?y<m[SK`'\R~Oe|(t-x+U@a%p!1_fZP0!Tb^?'%M1|"n9
 Fl{Ao~%X[Ec|bMlaN-3#x.e')nZ2/HHYSa2D[:bk#pj0(}\HpKeE}/GqUb3-1}lnUm6Et4?(
 gB5[*Z3Mu6o{Og.EJ))beY9oq9wcVU7_n}:I2JvCaa[5=&PI;x__["DL`uI}=s>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 08 Jul 1997 18:55:44 +1000
From: David Nugent <davidn@labs.usn.blaze.net.au>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  What options are you using on the "ls"?  "-l" causes lots of getpwuid()
>  calls.

I don't think he was using any options (otherwise it would require
a stat(), but he said it didn't). But, fyi, doing this, particularly
on a news spool where everything is owned by the same user/group,
there'd only ever be one getpwuid(). ls uses libc's pwcache function,
which caches user/group information.

>  > I thought I would try to investigate what the problem was, but, 
>  > before that; I'd send out the standard "has anyone seen/done anything
>  > in this area already?"   Has anyone else noticed an issue with
>  > readdir()?
>  
>    No.  I have over 20GB of news spool space.  It only takes a couple of
>  hours to expire.  Uptime is currently at 37 days, running 2.2.1

Same here (on a 2.2.2 news server). Expiry usually takes less than an hour,
and it isn't by any means a fast machine by today's standards (486DX4/100).
Obviously we don't carry a full news feed. :)

Regards,
David