This is a workflow app that contains 40,000 documents 132 views (7GB in size). The default view contains 21,000 documents. There are 2 scheduled agents that run every 10 minutes which move documents into views and send approval reminders. The database is FT indexed set to index documents immediately. This cannot be changed.
The database receives around 2000 writes/day. The update task is utilizing a high percentage of CPU. I want to add a 2nd Index, but I am concerned that will overwhelm the processor.
Is adding a 2nd indexer a good idea or a bad idea in this case?
TIA for any advice.
Regards,
Kristin
Subject: Why does it take users a long time to open intermittently?
I’m leaning towards problems with the index in this replica copy. The same DB on clustermates is running well. I’m also getting “Full Text message: Memory allocation error. errcode = 606” during indexing on just the one server.
Later today I will run fixup -F and updall -RX on the database to try to repair the index. Is it better to delete the FT files from the server or let them be updated?
Also this database can take up to 20 minutes to load intermittently for all users. I will try to open it every 15-20 minutes and 25% of the time, it takes a long time to open. The document counts are changing by less than 25 per session. What would cause this?