ND8 Performance Tweaks

Mindwatering Incorporated

Author: Tripp W Black

Created: 11/30/2007 at 03:59 PM

 

Category:
Domino Upgrades / Installations
Software (Re)Configuration

NSF Buffer Pools / UBM
This is the buffer pool for delayed writes to the NSF on disk.
The new default setting in ND8 for Windows and Linux is 512k. Previous ini settings existed for the 7 release.

PreShared Memory
Beginning in ND7, memory for the Domino server could be pre-allocated. That way if memory "ran out" on the machine, there should not be a Domino crash as it got all it's going to use at the startup. It is off by default and can be enabled via:
MEM_EnablePreAlloc=1 in NOTES.INI.

Opened Notes / Objects ( BLK_OPENED_NOTE )
Although LS recycles notes (performs garbage collection), the notes are still open. Therefore, they still are consuming memory until they expire.
Always close documents when looping through document collections.
Use either of the parameters below to specify the maximum amount of memory to be used by concurrent NoteOpen requests processed by the Domino server:
SERVER_MAX_NOTEOPEN_MEMORY_KB=<limit> -
The maximum number of bytes of memory allowed to be used by concurrently opened notes in the Domino server process. The value is specified in KB units. For example, setting a value of 10000 will result in a limit of 10,240,000 bytes.
SERVER_MAX_NOTEOPEN_MEMORY_MB=<limit> -
The maximum number of bytes of memory allowed to be used by concurrently opened notes in the Domino server process. The value is specified in MB units. For example, setting a value of 10 will result in a limit of 10,485,760 bytes.
If both notes.ini parameters are used, the SERVER_MAX_NOTEOPEN_MEMORY_MB parameter takes precedence.
* above from technote: swg21198511

Mail Rules
Tips for setting up mail rules (adapted from tip on Notes.net article)
1. There are two types of mail rules. If some seem to be working out of order, verify the rule types are sorted together. Refer to the admin help, or much better, to the Admin Boot Camp student course book for more information.
2. In your conditions, move the most common words or phrases to the beginning of your conditions list. For some formulas, the sooner the logic is successful, the less CPU is used because the searching stops once the correct set of conditions is met.
3: Move the most used rules to the top of the Configuration documents list. The rules are evaluated in the order in which they are listed. There are arrows to change the rules sequence. Note that all rules are evaluated with one exception-when a delete [or don't accept message] action is encountered. This stops processing of remaining rules. In ND7 there is also the stop processing rule to skip all other rules below the current rule. This can save a lot of time/system resources.
4. If only one user complains that a particular word needs to be added to the list, set up a rule in the user's personal mail file to search only messages sent to that user, instead of every mail message going to the server.
5. Don't search the body of the message unless it is really needed. Searching the body has the most impact on your CPU utilization. This sounds great, but if you are doing spam filtering with Domino, you're going to need to leave this enabled, too, for searching.

Anti-Spam Settings
For R5 amd Domino6.0x, Marc Alumbaugh of Rocking Chair Software, had a great tutorial on anti-spam configuration settings. Contact Marc at www.RockingChairSoftware.com for more information. For Domino 6.5 and updated for 7x, IBM has come out with a good 3 part tutorial for anti-spam. At this time the URL for this series is:
http://www.ibm.com/developerworks/lotus/library/ls-spam-smtp1/

previous page