MySQL search engine or ElasticSearch engine, which one to use ?
Thank you @marclaporte.
One important information for those of us using extensively trackers I see on the page is:
(MySQL Search)... There is a limitation on the number of tracker fields. The limitation is quite high (2000+), but when you hit it, you need to move to another engine because MySQL/MariaDB has a hard limit...
However, this information on the page is 10 years old. ?
I tested a 7400 trackeritems Tiki24 (my test Tiki, see above) with "mysql Ver 15.1 Distrib 10.3.35-MariaDB, for Linux (x86_64) using readline 5.1" and I didn't see, so far, any problem serving data (many plugin List and CustomSearch).
Asking chatGTP, that was his answer:
"in general, the maximum number of rows that can be stored in a single table in MySQL with InnoDB storage engine is determined by the maximum file size limit of the underlying file system. This limit is typically 2^64 bytes (16 exabytes) on most modern file systems.
Assuming that you have enough disk space, the number of tracker items you can use will also depend on the size of each item and the total amount of memory available on your server. It's also worth noting that MySQL has a limit on the total size of data that can be stored in a single table, which is determined by the maximum value of the innodb_file_per_table configuration setting, which is set to 4GB by default."
I don't have the skills or knowledge to deeply test and confirm or update the information on the page Unified Index Comparison.