IBM Notes and Domino wiki
All Wikis
All Forums
ANNOUNCEMENT: THIS WIKI IS READ-ONLY. Learn more...
Home
Product Documentation
Community Articles
Learning Center
IBM Redbooks
API Documentation
Search
Community Articles
>
Lotus Domino
>
Domino database performance
> Application properties that impact performance
Share
▼
Subscribe
▼
About the Original Author
Chad Scott
Contribution Summary:
Articles authored: 21
Articles edited: 21
Comments Posted:
1
Recent articles by this author
Transaction logging
Transaction logging is a critical configuration for maximizing database and server performance, and it is vital for ensuring data integrity and implementing a reliable backup and recovery architecture
Maintenance tasks
Domino provides two utilities that perform preventative maintenance for NSFs: Updall, and Compact. Understanding how, when, and why to run these tasks is a critical part of basic administration. Updall refreshes or rebuilds view and fulltext indexes, purges deletion stubs, and discards unused ...
Don't allow headline monitoring
Headline monitoring works similarly to RSS feeds; users subscribe to a database to receive notification on new and updated content that meets configurable criteria. In many cases, this functionality i
Don't allow simple search
Enable the Don't allow simple search advanced database property to prevent users from searching databases that do not have a full-text index. Because this type of search has a significant impact on th
Use LZ1 compression for attachments
LZ1 is a compression algorithm that provides improved performance over the older Huffman algorithm and should be enabled for all databases used by Lotus Notes Clients. Enabling the LZ1 attachment compression option does not modify existing documents that contain attachments that were compressed ...
Application properties that impact performance
Added by
Chad Scott
| Edited by
Mary Jrolf
on
August 15, 2008
|
Version 6
Actions
▼
Abstract
Abstract
No abstract provided.
Tags:
database properties
Every application contains several options that trade performance for additional functionality. To ensure maximum performance of your server and applications, it is critical to tune these so that additional features are configured only where necessary. Follow the rule of least privilege: if an application doesn't need a feature, disable it to maximize performance. We'll take a look at those features individually below. Unless otherwise specified, these settings are configured on the Advanced tab of database properties.
Don't maintain unread marks
Optimize document table map
Don't overwrite free space
Maintain LastAccessed property
Don't support specialized response hierarchy
Use LZ1 compression for attachments
Don't allow headline monitoring
Limit size of $UpdatedBy and $Revisions fields
Limit soft deletions
Enable design note compression
Enable document body compression
Don't allow simple search
Actions
▼
Attachments (0)
Attachments (0)
Edit the article to add or modify attachments.
Versions (5)
Versions (5)
Version Comparison
Compare version
6
Current 5
4
3
1
with version
6
Current 5
4
3
1
Compare selected versions
Version
Date
Changed by
Summary of changes
This version (6)
Aug 15, 2008, 11:29:49 AM
Mary Jrolf
5
Aug 15, 2008, 11:26:24 AM
Mary Jrolf
4
Aug 15, 2008, 11:22:39 AM
Mary Jrolf
3
Aug 15, 2008, 11:19:55 AM
Mary Jrolf
1
Jun 17, 2008, 3:19:24 PM
Amy Smith
Comments (0)
Comments (0)
Add comment
Copy and paste this wiki markup to link to this article from another article in this wiki.
Link:
Close
Go Elsewhere
Stay Connected
Help
About
IBM Collaboration Solutions wikis
IBM developerWorks
IBM Software support
IBMSocialBizUX on Twitter
IBMSocialBizUX on Facebook
Lotus product forums
IBM Social Business UX blog
The Social Lounge
Wiki Help
Forgot user name/password
About the wiki
About IBM
Privacy
Accessibility
IBM Terms of use
Wiki terms of use