Re: Archive is moving to auric / Incoming disabled
On Thu, May 11, 2000 at 09:11:10AM -0600, Jason Gunthorpe wrote:
> > Very unreliable stuff and also puts some strain on the server
> > the data is fetched from - if it has a large directory tree,
> > regenerating lsR with every change to the file system takes much
> > time. With ftp the client just asks the server for the listing and
> > that's it.
>
> Uh... Let me ask you a question. What is cheaper, generating a ls-LR
> once when your archive changes or several hundred times each day for
> each mirror. Particularly when it takes a good 4-5 mins to actually do
> a ls-LR :P
that depends. when a directory tree only changes rarely (e.g. only
during an rsync or mirror run), it's a big win to pre-generate the
ls-lR.gz files. that's what i do as part of my mirror run immediately
after i've mirrored debian (or whatever) to my local system.
when a directory tree changes often and unpredictably, you're better off
either not generating the ls-lR at all or making a decision that it's OK
for the ls-lR file to be 5 or 30 or 60 or whatever minutes out of date.
btw, reiserfs would probably take a lot less than 4-5 minutes to
do the ls-lR - it's amazing how fast it is for operations that are
traditionally slow on ext2 and other fs. i'm using it for squid cache
spools and for an experimental news spool - no problems so far. it'll be
a good thing when reiserfs is included in the standard kernel.
> The ftp client *should* already be using pre-generated ls-LRs.
mirror clients generally should. i don't know of any ftp clients that
do.
craig
--
craig sanders
Reply to: