Parameter:
UPDATE_FULLTEXT_THREADShort description: Moves full-text indexing out of the general
Update task into its own thread – reduces contention between view and full-text indexing.Profile
Parameter | UPDATE_FULLTEXT_THREAD |
Category | Performance / Memory |
Component | Server |
Available since | 10.0 |
Supported versions | 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | 0 = shared (default), 1 = dedicated FT thread |
Description
The
Update task maintains both view indexes and full-text (FT) indexes. On servers with many FT-indexed databases, the shared lock can become a bottleneck. With UPDATE_FULLTEXT_THREAD=1, FT updates run on their own thread – view updates are no longer blocked.Recommended for servers with heavy search usage (helpdesk DBs, knowledge bases).
Example configuration
UPDATE_FULLTEXT_THREAD=1
Notes & pitfalls
- Requires sufficient CPU capacity – the additional thread runs in parallel.
- Combines with the
UPDATE_*_THREADfamily andFT_NO_FILTERINGoptimizations.
- On I/O-constrained servers the effect may be negligible – tune storage instead.
- Compare baselines via
show stat update.*andshow stat ft.*.
- The change takes effect after restarting the
Updatetask or a server restart.