Domino Application Performance : Database properties Part 1
Don’t maintain unread marks.
If check this option in database properties, unread marks will not be tracked in your application regardless of the settings you have for each view. I’m used to track the time client_clock enabled database and I can see that I was surprised. For large application (about 20 GB with 200,000 documents), my Notes client could open the database in about five seconds without unread marks, including network traffic. With unread marks turned on, I had to wait an additional six seconds or more. This additional time was spent in GET_UNREAD_NOTE_TABLE and RCV_UNREAD. With unread marks turned off, these calls aren’t made.
In a smaller database (less than 1 GB), I saw savings of maybe 0.5 seconds with unread marks turned off. This faster to open that database with or without unread marks compared to the larger database. Therefore, you should consider whether the applicant is not required the unread marks feature before you roll it out into production.
Optimize document table map.
This feature has not changed from the past few years, Lotus Notes Domino’s. This feature is designed to speed up the index view using the Domino directory structure, etc. (In other words, they contain many documents that use one form and a small number of documents using a different form. Think of Person documents versus Server documents in the Domino Directory.)
Instead of checking every document note to see whether or not it should be included in a view index, I make two passes. The first pass merely checks to see if the correct form name is associated with that document. The second pass checks for the various other conditions that must be met to include this document note in the view index.
Viewed 7356 times by 1821 viewers
