Lately, we are experiencing performance and load issues in our iSeries, causing that the server (and iSeries) get a bad performance. In some occasions the Domino server shuts down by it-self, in others we need to kill it.
Usually, bad behavior start at night or during the weekends when we have our LEI activity scheduled. After monitor the Job Activities in the iSeries, looks like the task responsible for this is the Indexer (UPDATE) that is executed by the server after the LEI activity finished.
I did a test in our Development server, and the UPDATE took between 50% and 60% of CPU after the LEI finished.
Does anyone have an idea why - or how we can figure out why - the UPDATE Task takes so much CPU?
BTW, we are upgrading to 7.0.2 because this issue is getting critical.
Subject: Indexer (UPDATE) Task taking too much resources!!!
Irely,
From your description it sounds as though you have LEI making so many data changes that your indexer has to run very hard for a long time to update your views.
You might want to get a sense of how many data changes are in fact being made.
Domino can be effective at managing large data loads, but you do have to be careful about how the data is updated.
Subject: RE: Indexer (UPDATE) Task taking too much resources!!!
Thanks for reply.
The LEI activities were set up here as Direct Transfer, with overwrite current data. That is why all documents are created each time.
I am re-creating them to be Replication activities, but I am still working to identify which is the correct setting that will avoid update all the documents. Do you have experience with timestamp or with the correct setting to replicate only modifications?
The Source tables are DB2 and I do not have a field with Last Update.