Lotus Domino: Tunning English: Difference between revisions
(New page: 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 # Have...) |
|||
Line 66: | Line 66: | ||
Domino.Cache.Design.HitRate = 81.960226776015 | Domino.Cache.Design.HitRate = 81.960226776015 | ||
Domino.Cache.Design.MaxSize = 128 | 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 the'''Hitrate''' is near 100%, and'''DisplaceRate''' is 0%. Increasing the value of the field'''Maximum cached designs''' improves response-time. | |||
== Cached User Info == | |||
To optimize the response time keeps Domino design elements in memory. | |||
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 | |||
{| border="1" | |||
| | |||
'''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. | |||
|} | |||
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'''). | 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 the'''Hitrate''' is near 100%, and'''DisplaceRate''' is 0%. Increasing the value of the field'''Maximum cached designs''' improves response-time. | The optimal value for the'''Hitrate''' is near 100%, and'''DisplaceRate''' is 0%. Increasing the value of the field'''Maximum cached designs''' improves response-time. |
Revision as of 01:51, 10 September 2010
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
- Have an implementation plan
- Know your infrastructure
- Divide the compounds
- Platform
- Notes Mail Statistics
- Network report
- Server Load Statistics
- Have a baseline reference
Disabling the Collection of Statistics Platform
Domino statistics collection platform to display the Administrator. The collection does not consume much resources, but we're talking about tuning.
To disable the collection utize the following parameter in NOTES.INI.
Platform_Statistics_Disabled = 1
Reasons:
- You do not want to collect statistics
- On partitioned servers (DPAR), each server collects the same statistics. You can enable only in one partition and disable the others.
Cache Design Elements
To optimize the response time keeps Domino design elements in memory.
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 designs |
Enter the number of database design elements to cache for users. The default is 128. When a user opens a database, Domino maps each design element name to an identification number. This mapping procedure takes time. Use this field to Specify how many elements you want to store in memory so the next time the user accesses That element, it is Immediately available. |
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.
Cached User Info
To optimize the response time keeps Domino design elements in memory.
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. |
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.