Well, from my experience (with about million of records) I highly suggest updating the catalog instead of a full reindex. Just think of the process that OpenBD/Lucene has to do (full index would mean query ALL records and cfindex them vs. a simple update of only a few records).
On Thu, Apr 22, 2010 at 5:08 PM, Jason King <[email protected]> wrote: > I'm just wondering if it would be better to have it rebuild the entire > catalog, from scratch, every 10 minutes, and just copy the new version over > to the webservers, rather than actually updating the master catalog > everytime there is a new entry, and then rsync'ing it to the webserver copy > every time. Fortunately, I have many smaller catalogs vs one bigger one > (many different facets of data in the site). However, over time, I might > expect some of the catalogs to have several million entries. In this case, I > could lengthen the distance between intervals (say 20 minutes instead of > ten), or just beef up the catalog server so it gets the jobs done quicker. -- See for yourself how easy it is to manage files today. Join the revolution! Razuna SaaS On-Demand - Hosted Digital Asset Management Solution http://www.razuna.com/ Razuna - Open Source Digital Asset Management http://www.razuna.org/ Follow us on Twitter http://twitter.com/razunahq -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
