Hi,
We have a database with 2 agents.
Agent1. run every 5 minutes that read and process documents, usual elapse time is about 60 seconds.
Agent2. run every Saturday night, it deletes about 20000 documents.
After agent Agent2 run completed, agent Agent1 kicked off taking 30 minutes to complete (where normally only 60 seconds).
I wonder what Domino was doing after Agent2 that makes Agent1 so slow and any way to make Agent1 stays within 60 seconds?
Your assistance in this matter is greatly appreciated
Subject: Deletion Stubs
I would close change the deletion stub interval http://www-01.ibm.com/support/docview.wss?uid=swg21095683 http://www-01.ibm.com/support/docview.wss?uid=swg21095683
If you don’t have a replica for this db I would set it to 0. Naturally if there is a replica set it to a safe number that normal replication would occur.
Subject: Domino after large document deletion
I presume that you have many views in your database, or views with complex formula.
Usually, when you update or delete large data, Domino updates views and this could be a nightmare if you have a large database size and many views.
It might also be the Full Text index, running and updating the Full Text Search.
In order to be sure what’s causing the problem, you can set the parameter log_update =2 that should tell you the time each view is taken to be updated in the Domino Console. This will give you an idea.
Just a quick note, be sure to run compact from time to shrink database size.
Hope this helps.