HCL
Skip to main content  
 
   


SPRTechnote


New Update Task Algorithm Has Increased Resource Usage in Notes/Domino 6.0.x

Technote Number: 1148468


Problem:
The update task in Domino 5.0.x pauses 5 seconds between each update and
performs the tasks in an unfair order. On many servers, the queue of update
tasks grew very large so that updates were not done in a timely manner.

In 6.0, to solve this problem, the updates are now performed in a fair order,
meaning that update requests are done in date/time order according to when they
were submitted. Additionally, the default is to not pause at all between
update tasks. However, in some cases it has been reported that the update task
takes more machine resources in 6.0.x than it did in R5.

This issue was reported to Quality Engineering and has been addressed in
Notes/Domino 6.0.3 and 6.5. The default of 5 seconds between updates has been
restored to reduce the amount of system resources the Update task consumes.
Updates continue to be processed in a fair order (unlike in R5.x).

Excerpt from the Lotus Notes and Domino Release 6.0.3 MR fix list (available at
http://www.lotus.com/ldd

SPR #PMIA5N6HKJ - Reduced resource consumption of the Indexer Task.

Supporting Information:
The default delay between update tasks can be changed via the following setting:

UPDATE_IDLE_TIME=n (in seconds)

Note: Decreasing the value of this setting will allow the update task to
perform more updates in any time period, meaning the updates occur in a more
timely manner; however, this is at the cost of machine resources.
More >





  Document options
Print this document
Print view

  Search
Search Advanced Search


  Fix list views

 RSS feeds   RSS
Subscribe to the fix list

  Resources
Using this database
View notices

  HCL Support
HCL Support


    About HCL Privacy Contact