Lotus Domino: Tuning English

Tuning

This wiki will be creating a series of articles outlining best practices for Lotus Domino environment.

I ask you to always return to this article will be updating as usual.

Steps


 * 1) Have an implementation plan
 * 2) Know your infrastructure
 * 3) Divide the compounds
 * 4) Platform
 * 5) Notes Mail Statistics
 * 6) Network report
 * 7) Server Load Statistics
 * 8) Have a baseline reference

= GENERAL =

GENERAL: Update Index and Full Text
Tuning tips for Index and FullText

UPDATE_FULLTEXT_THREAD=1 UPDATE_IDLE_TIME=4 FTG_USE_SYS_MEMORY=1 FTUPDATE_IDLE_TIME=4 FT_Index_Ignore_Attachment_Types=*.nsf,*.ntf,*.tif,*.sys,*.pag,*.img,*.wav,*.gif,*.jpg,*.dll,*.tar,*.exe,*.zip,*.au,*.mpg,*.mov,*.mp3,*.cca,*.dbd,*.p7m,*.p7s,*.wpl,*.bmp

Since version 5.0.5, Domino disable by default to following Attachment types: .NSF, .NTF, .SYS, .PAG, .IMG , .WAV , .GIF, .JPG, .DLL, .TAR, .EXE , .ZIP, .AU , .MPG, .MOV, .MP3.

GENERAL: Disable BCC group expansion
The 'DISABLE_BCC_GROUP_EXPANSION' setting will disable BCC group expansion, thereby improving mail server performance.

DISABLE_BCC_GROUP_EXPANSION=1

DISABLE_BCC_GROUP_EXPANSION

GENERAL: Reduce log
Reduce log output and write to log.nsf LOG_MAILROUTING=10 LOG_SESSIONS=0 Log_replication=0

HTTP: Cache Design Elements
To optimize the response time keeps Domino design elements in memory.

Example To find out if you need to change this parameter, run the following command

> Show stat domino.cache.design .* Domino.Cache.Design.Count = 128 Domino.Cache.Design.DisplaceRate = 18.0328294698918 Domino.Cache.Design.HitRate = 81.960226776015 Domino.Cache.Design.MaxSize = 128

Observing these numbers we can deduce that the value of elements (Count) has reached the maximum (MaxSize), so elements in this cache are discarded ( DisplaceRate).

The optimal value for theHitrate is near 100%, andDisplaceRate is 0%. Increasing the value of the fieldMaximum cached designs improves response-time.

HTTP: Cache User Info
To optimize the response time keeps Domino design elements in memory.

Example

To find out if you need to change this parameter, run the following command

> Show stat domino.cache.user* Domino.Cache.User Cache.Count = 68 Domino.Cache.User Cache.DisplaceRate = 0 Domino.Cache.User Cache.HitRate = 73.258795221749 Domino.Cache.User Cache.MaxSize = 64

Observing these numbers we can deduce that the value of elements (Count) has reached the maximum (MaxSize), so elements in this cache are discarded ( DisplaceRate).

The optimal value for theHitrate is near 100%, andDisplaceRate is 0%. Increasing the value of the fieldMaximum cached designs improves response-time.

- HTTP Threads:

Domino.Config.ActiveThreads.Max

CPU: Utilization
Platform.Process.ActiveDomino.TotalCpuUtil Platform.Process.traveler.1.PctCpuUtil Server.CPU.Count

-> PctCpuUtil / CPU.Count ~ aprox CPU usage by traveler task

Full Text Search
= TRAVELER =

Migrated to Lotus Traveler: Tuning English

= SERVER =

SERVER: NSF Buffer Pool
Buffering Database I/O

Example

To find out if you need to change this parameter, run the following command

> Show stat Database.Database.BufferPool.* Database.Database.BufferPool.Maximum.Megabytes = 1024 Database.Database.BufferPool.MM.Reads = 24 Database.Database.BufferPool.MM.Writes = 7 Database.Database.BufferPool.Peak.Megabytes = 1023 Database.Database.BufferPool.PerCentReadsInBuffer = 98.21

If the Database statistics Database.Database.BufferPool.PerCentReadsInBuffer is lower than 97%,then you should consider tuning this parameter.

SERVER: NSF Cache
To minimize the time lags involved with opening and closing databases on a server, each server uses a database cache.

The Notes.ini NSF_DbCache_Maxentries control how many databases can reside in the cache at a maximum.

This NSF database cache is limited to:


 * 10000 entries = Domino 5.x and 6.x.
 * 20000 entries = Domino 7.x and higher

Example To find out if you need to change this parameter, run the following command

> Show stat Database.Database.BufferPool.* Database.Database.BufferPool.Maximum.Megabytes = 1024 Database.Database.BufferPool.MM.Reads = 24 Database.Database.BufferPool.MM.Writes = 7 Database.Database.BufferPool.Peak.Megabytes = 1023 Database.Database.BufferPool.PerCentReadsInBuffer = 98.21

If the Database statistics Database.Database.BufferPool.PerCentReadsInBuffer is lower than 97%,then you should consider tuning this parameter.

> Show statDatabase.DbCache.* Database.DbCache.HighWaterMark = 2227 ... Database.DbCache.MaxEntries = 3072 ... Database.DbCache.OvercrowdingRejections = 0 Database.DbCache.Size = 10003

If the Database statistics DbCache.OvercrowdingRejections is high, then you should consider tuning this parameter.

SERVER: Concurrent Tasks
PUT INFO HERE

UPDATERS: Updall Tasks
PUT INFO HERE

ROUTER: How many Mailboxes?
How many Mailboxes is necessary for my Domino Server

ROUTER: RouterDbCacheSize
Represents the number of entries allocated for the router database cache. If not used, the default is based on NSFBufferPoolSize (three per MB), i.e. three times bigger than NSFBufferPoolSize, and the maximum is capped to 20000 entries at startup, but reallocation may occur and the number of 20000 entries could exceed it. In brief: it represents a cache of opened mail database handles.

CLUSTER: Cluster Replicator
To prevent the replicas of the cluster de-synchronized, increasing the amount of tasks clrepl through the Notes.ini variable

Example

Para saber se é necessário alterar este parâmetro, execute o seguinte comando > show stat replica.cluster.* ... Replica.Cluster.SCR.QueueDepth.Avg = 0 Replica.Cluster.SCR.QueueDepth.Max = 155 ... Replica.Cluster.SecondsOnQueue = 2 Replica.Cluster.SecondsOnQueue.Avg = 18 Replica.Cluster.SecondsOnQueue.Max = 2558 ... Replica.Cluster.WorkQueueDepth = 0 Replica.Cluster.WorkQueueDepth.Avg = 13 Replica.Cluster.WorkQueueDepth.Max = 698

= Ver também =


 * IBM Domino: Monitoring the health of you Domino Server using HTTP and show stats


 * Mais artigos sobre IBM Domino e Notes
 * More articles about IBM Domino e Notes