Technote Number: 1108358
Problem:
This issue was reported to Lotus software Quality Engineering and has been
addressed in Domino 5.0.13 / 5.0.13a and Domino 6.0.2.
Excerpt from the Lotus Notes and Domino Release 5.0.13 / 5.0.13a MR and 6.0.2
MR fix lists (available at http://www.ibm.com/developerworks/lotus):
Server
SPR# CMCY5FFTN8 - Performance improvement: correction for poor hashing
algorithm used to find process context block data in MatchObj code. Process
context block data is used extensively by all Domino tasks. This has been
changed in 6.0.2 and 5.0.13.
This issue was also partially addressed in Domino 5.0.12. It was found that
the contention was from making OS calls to reobtain the same information over
and over, rather than getting it once and keeping it in memory for everybody.
In Domino 5.0.12, a new performance setting can be enabled in the NOTES.INI of
the Domino server:
ENABLE_LOCAL_PCB=1
This should prevent the contention in MatchObj, by caching the information for
each process.
NSD shows many threads in:
glink.select() at 0xd07efbc0
unix_usleep(??) at 0xd07efb48
unix_usleep(??) at 0xd07efb48
OSDelayThread(??) at 0xd076a1c0
OSLockSpin(??) at 0xd076e2f8
OSLockReadSem(??) at 0xd076f4cc
MatchObj(??, ??, ??, ??, ??, ??, ??, ??) at 0xd07aed28
OSStaticMem(??, ??) at 0xd07b2b68
OSProcessShouldQuit() at 0xd076976c
MQIsQuitPending(??) at 0xd08e5448
MQGetExtended(??, ??, ??, ??, ??, ??, ??) at 0xd08e5c88
ProcessEvents() at 0x10002b00
pth_pthread._pthread_body(??) at 0xd004b3fc More >
|  |
|
|
|
|
|