Loading...
 

Unified Index Comparison

The Search and List from Unified Index has support for multiple engines. While all of them offer the same general functionality and connect to various functionality such as the content search, PluginList, PluginCustomSearch and various others, they will have different performance characteristics and some may offer additional features.

As a general rule, the engine can simply be switched and the index rebuilt without any additional change to the configuration.

The default settings are fine for all but the biggest Tiki projects (top 1%). If rebuilding your index takes less than 30 minutes, you generally have nothing to worry about.

There are so many parameters that we can't predict at how many pages, files or tracker items that you will hit an issue. It depends on many factors, including

  • Server resources (RAM, CPU, etc.)
  • Quantity of data
  • Type of data (tracker items vs wiki pages, etc.)
  • Number and type of tracker fields
  • Version of Tiki and how it's configured
  • Version of database and how it's configured
  • Etc.


So just stay with the defaults until/unless you hit a problem. Ex.:

  • A full text search becomes slow.
  • Error messages related to having too many fields


If you have or plan to have a big Tiki instance and you are concerned if Tiki will scale to your use case, you can use Faker to generate fake data on your server. You can also reach out to experienced folks.
For community support: https://gitter.im/tiki-org/community
For professional services: https://evoludata.com/

List Slides
Export PDF
Handouts
Exit Slideshow
Unified Index Comparison The Search and List from Unified Index has support for multiple engines. While all of them offer the same general functionality and connect to various functionality such as the content search, PluginList , PluginCustomSearch and various others, they will have different performance characteristics and some may offer additional features. As a general rule, the engine can simply be switched and the index rebuilt without any additional change to the configuration. The default settings are fine for all but the biggest Tiki projects (top 1%). If rebuilding your index takes less than 30 minutes, you generally have nothing to worry about. There are so many parameters that we can't predict at how many pages, files or tracker items that you will hit an issue. It depends on many factors, including Server resources (RAM, CPU, etc.) Quantity of data Type of data (tracker items vs wiki pages, etc.) Number and type of tracker fields Version of Tiki and how it's configured Version of database and how it's configured Etc. So just stay with the defaults until/unless you hit a problem. Ex.: A full text search becomes slow. Error messages related to having too many fields If you have or plan to have a big Tiki instance and you are concerned if Tiki will scale to your use case, you can use Faker to generate fake data on your server. You can also reach out to experienced folks. For community support: https://gitter.im/tiki-org/community For professional services: https://evoludata.com/