InnoDB System Variables significant in a search context, such as the English words “a”  and “to” . For content using a CJK (Chinese, Japanese, Korean) character set, specify a value of 1. For more information, see Section 12.10.6, “Fine-Tuning MySQL Full-Text Search” . Number of words to process during each  OPTIMIZE TABLE  operation on an  InnoDB FULLTEXT  index. Because a bulk insert or update operation to a table containing a full-text search index could require substantial index maintenance to incorporate all changes, you might do a series of  OPTIMIZE TABLE statements, each picking up where the last left off. For more information, see Section 12.10.6, “Fine-Tuning MySQL Full-Text Search” . The  InnoDB  full-text search query result cache limit (defined in bytes) per full-text search query or per thread. Intermediate and final  InnoDB  full-text search query results are handled in memory. Use innodb_ft_result_cache_limit  to place a size limit on the full-text search query result cache to avoid excessive memory consumption in case of very large  InnoDB  full-text search query results (millions or hundreds of millions of rows, for example). Memory is allocated as required when a full-text search query is processed. If the result cache size limit is reached, an error is returned indicating that the query exceeds the maximum allowed memory. The maximum value of  innodb_ft_result_cache_limit  for all platform types and bit sizes is 2**32-1. 3252 • innodb_ft_result_cache_limit • innodb_ft_num_word_optimize Command-Line Format --innodb-ft-num-word-optimize=# System Variable innodb_ft_num_word_optimize Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 2000 Minimum Value 1000 Maximum Value 10000 Command-Line Format --innodb-ft-result-cache-limit=# System Variable innodb_ft_result_cache_limit Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Integer Default Value 2000000000 Minimum Value 1000000 Maximum Value 2**32-1