Tried optimizing the collection and the server had a fit. There was some sort of conflict with ASP.net so both services had to be restarted. The collection containing the files worked fine, but the content in the database didn't get to finish (due to server issues).
In the code, it had two lines that were re-indexing the collections each time the search was run. After commenting this out, the search was still just as slow.
Reindexing every search sounds like a disaster. Verity should only be updated and optimised.
Verity is an optimised read only database in effect. You *must* keep the collection optimised or it will fragment over time (as you add new content) and become slower and slower -- to the point of being unusable.
I was thinking about purging the database collection and re-indexing this afternoon when server traffic dies down. Do you think this will help at all?
How are you reindexing the database collection? Are you looping over the CFINDEX tag? This will lead to very high fragmentation and very low performance. If you post the indexation code I'd be happy to help.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
