Many worklists provide a full-text1 search filter to match record content based on terms and phrases.
For instance, you may need to search your email history for the phrase: "facebook ads" receipt.
By default, these searches are implemented as FULLTEXT indexes in MySQL2. We’ve done a lot of optimization to keep these searches efficient, and it “just works”. However, MySQL isn’t an optimal search engine for larger environments.
As you scale, you may decide to switch to Elasticsearch or Sphinx. We support both. These options require you to manage an additional service, but they’re much faster and provide you with more control over how your content is indexed.