Search
Contribute
Navigation
- ACL
- administration
- AJAX
- authentication
- Best Practice
- calendaring & scheduling
- certificate
- certificate authority
- Citrix
- Client deployment
- Client setup configfile
- composite apps
- compression
- concepts
- database
- database properties
- Deployment issues
- diagnostics
- directory
- Domino Server Install
- Eclipse
- encryption
- FIPS
- full text indexing
- groups
- id
- ID file
- images
- install
- Java
- Javascript
- journal
- language pack
- learning
- live text
- logging
- mail file
- mail router
- mail rules
- mail.box
- memory
- messaging
- MIME
- mobility
- Monitoring
- My Widgets
- network
- notes.ini
- NSF performance
- obsolete notes.inis
- ODS
- Partitioned server install
- performance
- plug-ins
- Policies
- replication
- resources
- Resources database
- search
- security
- SMTP
- s/mime
- templates
- TNEF
- transaction logging
- tutorials
- update
- upgrade
- views
- web
- @ formulas
Go elsewhere
UPDATE_FULLTEXT_THREAD
Article information
| Server Notes.inis
best practice , full text indexing , views |
Harry Peebles 05/20/2008 |
Amy Smith 06/11/2008 |
|
|
Explanation:
Full-text indexing operations occurring on the Domino server can cause performance degradation. By default, the full-text indexing function is performed by the update threads that are responsible for updating views. This can quickly translate into a bottleneck for update processing on the Domino server.
Setting the Update_Fulltext_Thread parameter to 1 allows use of a separate thread to do full text indexing so that long full text indexes don't delay view updates. By default, view updates and full text index updates are driven by the same thread. View updating will still work in "updall." Additionally, to decrease latency between full-text indexing operations, set the FTUPDATE_IDLE_TIME parameter to a value less than 5 (which is the default behavior)
Recommendation:
Set UPDATE_FULLTEXT_THREAD=1 and FTUPDATE_IDLE_TIME < 5 in your configuration to improve server performance
Related Settings:
FTUPDATE_IDLE_TIME, FTUPDATE_IDLE_TIME_MS, UPDATE_DISABLE_FULLTEXT
References:
Technote 1247507
Compact operation not performed immediately on a busy server
http://www.ibm.com/support/docview.wss?uid=swg21247507
Domino Configuration Tuner:
This setting is included in the DCT catalog of best practices as of Domino 8.5
Full-text indexing operations occurring on the Domino server can cause performance degradation. By default, the full-text indexing function is performed by the update threads that are responsible for updating views. This can quickly translate into a bottleneck for update processing on the Domino server.
Setting the Update_Fulltext_Thread parameter to 1 allows use of a separate thread to do full text indexing so that long full text indexes don't delay view updates. By default, view updates and full text index updates are driven by the same thread. View updating will still work in "updall." Additionally, to decrease latency between full-text indexing operations, set the FTUPDATE_IDLE_TIME parameter to a value less than 5 (which is the default behavior)
Recommendation:
Set UPDATE_FULLTEXT_THREAD=1 and FTUPDATE_IDLE_TIME < 5 in your configuration to improve server performance
Related Settings:
FTUPDATE_IDLE_TIME, FTUPDATE_IDLE_TIME_MS, UPDATE_DISABLE_FULLTEXT
References:
Technote 1247507
Compact operation not performed immediately on a busy server
http://www.ibm.com/support/docview.wss?uid=swg21247507
Domino Configuration Tuner:
This setting is included in the DCT catalog of best practices as of Domino 8.5
Comments



