Re: [greenstone-users] Problem with build process

From Michael Dewsnip
DateMon, 10 Jan 2005 13:41:55 +1300
Subject Re: [greenstone-users] Problem with build process
In-Reply-To (41C776C0-5010309-realss-com)
Hi Lian,

> We meet a problem with greenstone installation on a
> low-performance pc. The pc ram is so limited that it need a terrible
> long time to build a collection if the collection has a lot of files.
> We need to add new files into the same collection every time. The
> collection becomes very big. So everytime after done import, it needs
> quite a long time to build the collection.
> My question is that is it possible when import a file into an
> existed collection, it doesn't rebuild the collection with all the
> files. It will save a lot of time if just rebuild the *new* file into
> the existed collection.

I agree this would be nice, but unfortunately the indexers that
Greenstone uses don't fit this model, since they don't allow the indexes
to be added to. If you're interested, you can get the gory details from
the "Managing Gigabytes" book, by Witten, Moffat & Bell.

There isn't an easy way around this, since it is a fundamental aspect of
Greenstone's design, but there are a few things you can do to help:

- Make sure you're only building the indexes you need
- Keep the collection small until you have the design finalised, then
rebuild with all the documents
- Set up a process to automatically rebuild the collection every night
- Upgrade your machine, or use a faster one!