Table of contents
Performance should always be considered when developing applications. This section contains best practices for performance, but there may be many more.
Using Summary Reports instead of views
While [View Indexing] allows caching of view content, which facilitates faster access to Domino data, the repeated runtime queries of the View Index for certain reusable data subsets can cause undue stress on the server as well as impact the user experience. To achieve the same functionality, we discuss the creation and maintenance of a Summary Report
. A Summary Report
is a document that contains metric data and other analytic content. Applications can use this report to facilitate low-cost metadata queries against large data collections.
Concurrent Web agents
By default, agents that run as a result of HTTP requests are run one after the other in a sequential, serial manner. This can be a huge performance bottleneck if you plan to use agents in your application, so you may have to modify the server configuration to allow Web agents to run concurrently. This option is in the Server Document on the Internet Protocols -> Domino Web Engine
tab. You must reload the HTTP task in order for the change to take effect.