Lotus Traveler: Tunning English

LOTUS TRAVELER THREAD POOLS

Lotus Notes Traveler has four thread pools that can be tuned:

Prime sync threads - Determine if changes to user mail files need to be synchronized to user devices.
Device sync threads - Synchronize data between Domino mail servers and user devices.
Worker threads - Used internally in the device synchronization process.
HTTP threads - Used by the HTTP task, one per HTTP connection.

Thread pool name	Default Value
TSS_PRIMESYNC_THREADS	10
TSS_SYNC_THREADS	50
WORKER_THREADS	100 (should always be double the TSS_SYNC_THREADS value)
HTTP Threads	100 on Windows 32-bit machines 400 on Windows 64-bit machines)

The following are general guidelines for the relationships between the number of threads in each of the thread pools.

Prime sync threads should be much less than the number of device sync threads; normally the prime sync default of 10 threads should be adequate.
Worker threads should be double the number of device sync threads.
HTTP threads should be 1.2 times either the number of device sync threads or the number of ActiveSync devices, whichever is larger.

Domino data directory\traveler\cfg\NTSConfig.xml.

Lotus Traveler Tuning performance of the server

Cache User Info - HTTP Maximum Cached Users - 64 bits only

To optimize the response time keeps Domino design elements in memory.

Tune

To change the parameters of Web Cache, Open the server document and go

Internet Protocols → Domino Web Engine → Memory Caches.

and change the field value

Field	Description
Maximum cached users	Enter the number of users to cache. The default is 64. After a user successfully authenticates with a server, Domino stores in memory the user's name, password, and the list of groups to which the user belongs. Use this field to increase the number of users for whom Domino stores this information.

Statistics

Push.Devices.Total

Interpretation

Push.Devices.Total = 2455

Reference

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.