Indexing usually makes queries slow. If you have fast disks, indexing will use 100% of the CPU, otherwise it will use 100% of the disk bandwidth. In any case, the requests will be slow.
For this, the master / slave configuration is the standard solution. Slave servers are for search queries. The only time they slow down after replication is when new search engines are created with new caches.
The master / slave configuration may not make indexing much faster, but it will avoid slow query performance. There has been work on multithreading indexing, so you can try several indexing tasks at once. This will not help if the bottleneck is the IO drive, only if it uses 100% of one processor.
Trie fields are great for range queries. I doubt that they will greatly influence the speed of indexing.
Finally, you can adjust spelling options. Spelling can be a lot of work, and you can get good results with different, less expensive options.
Walter underwood
source share