On Mon, 3 Feb 2003, Timothy Smith wrote:
> that was with the -e switch (see inline).
Oh, right. Everytime I've indexed with -e the memory consumption stays
quite low. Do you see *lots* of temporary files in the current directory
Try indexing with -v3 and see if there's a single file it's getting hung
up on. IIRC the memory savings with -e are per file, so it could be one
big file causing the problems.
Anyone else experience high memory usage when using -e?
> >From: Bill Moseley <firstname.lastname@example.org>
> >Reply-To: email@example.com
> >To: Multiple recipients of list <firstname.lastname@example.org>
> >Subject: [SWISH-E] Re: swish memory/perf
> >Date: Sun, 2 Feb 2003 18:23:44 -0800 (PST)
> >On Sun, 2 Feb 2003, Timothy Smith wrote:
> > > Hi,
> > > Love swish but seem to be having some issues with indexing a larger
> > > amount of documents.
> > >
> > > Directory has 29032 files, total size 3.1GB
> > > Config file at end of message.
> > > /usr/local/bin/swish-e -e -i /mydir -c file.config
> > > version: 2.2.3
> > >
> > > Basically the process grew to around 600MB in size (exceeding my 128MB
> > > over 21 hours and I finally killed it before it used all my swap.
> > >
> > > Any thoughts?
> >You don't want to run out of RAM. Short of adding more memory (128M isn't
> >much), what happens when you use the -e switch? I would think you should
> >be able to index 30K files in a lot shorter time than 21 hours. More like
> >a few minutes.
> >Bill Moseley email@example.com
> Protect your PC - get McAfee.com VirusScan Online
Bill Moseley firstname.lastname@example.org
Received on Tue Feb 4 02:41:20 2003