We are extremely proud to announce that the notes.ini Reference Database contains not more then 1.500 valid entrys and the database is growing every day.

Do you sometimes need to compare two notes.ini files with each other but you doesn´t like to install a 3rd party program on your PC, or the 3rd party program doesn´t work with notes.ini files? Then you should have a look on the free "online Notes.ini comparison tool" on this website.

Note:

Some user who created a account in the past for this website have seen this tool in the menu. So this tool isn´t new to them. The reason for this was, that the tool was hidden to unregistred users, because it was in a pre-beta state and could be tested for registred users. These tests are now over.

Based on several years of experience evaluating custom Notes applications to diagnose performance-related issues, IBM compiled the most common properties that can affect application performance. On two websites they cover the database, view, and form properties known to affect application performance. They will tell you when to use and when not to use certain properties for best performance results, and where applicable, IBM will provide you with alternative solutions.

Application Performance Tuning, Part 1

This article looks at the database, view, and form properties that most commonly affect how well your applications perform.

Application Performance Tuning, Part 2

This article looks at coding practices that can improve application performance. It also examines some common LotusScript methods to see which ones perform best under different conditions.

Note:

These articles aren´t brand new ones. But they include some good points for application performance.

In Lotus Domino, the Event Correlation cache is used as a holding area in which Domino Domain Monitoring (DDM) events are correlated to previously encountered events. When this cache grows to its maximum size, the server reports the following error:

2009-01-27 23:04:29   Event: Error adding event document to Domino Domain Monitoring: Event correlation cache is full. You can increase its size via the NOTES.INI setting EVENT_CORRELATION_POOL_SIZE.

Maybe you tried to change the EVENT_CORRELATION_POOL_SIZE notes.ini variable, but that doesn´t solve your problem. Even with the maximum configured pool size from 100MB (EVENT_CORRELATION_POOL_SIZE=104857600), you may still see the above error. This occurs because Domino creates cached documents that are 2MB in size and the server allows a maximum of 200 cached documents by default.

Since 2MB x 200 is greater than the maximum allowable pool size, the error can occur unless additional parameters are enacted to control the document size and/or the maximum number of cached documents. The following notes.ini parameters are available for these purposes.

DDM_MAX_NOTE_CACHE (number of documents in the cache)
DDM_MAX_DOCSIZE_MB (size in megabytes of documents in the cache)

To finetune these values you need to check your ddm.nsf. The best way is to create a new view which lists all documents and enter a new column which show the size from the documents. The biggest document in this view can be used to finetune the DDM_MAX_DOCSIZE_MB value. In my example the biggest document is a 712KB big document (a event which is 2 years old but reopen from time to time), all the other documents are smaller (+-250KB).

To ensure now that the Event Correlation cache will not be exhausted when configured to the maximum 100MB size, I use these information and the parameters from above so that the following formula is true:

DDM_MAX_NOTE_CACHE x DDM_MAX_DOCSIZE_MB <= 100

 Means:

DDM_MAX_NOTE_CACHE=100

DDM_MAX_DOCSIZE_MB=1

EVENT_CORRELATION_POOL_SIZE=104857600

After you set these values (via set config ... on the console) you need to restart the events task.