...
In the release 3.5, we have introduced the back-end indexing. How should an administrator choose between the two indexing engines?
...
How should a customer prepare the transition to the Indexation V2?
Check whether you are using baselines. If yes, make your key users aware that the contents of requirements indexed before and after the move to Indexation V2 won’t be comparable, due to many tiny changes in the output HTML.
Check whether you are using the app named “Scaffolding”. If so, then the support for Scaffolding is only implemented in 3.9.0, with limitations described in https://requirementyogi.atlassian.net/browse/RY-1160
What is the recommended setting?
...
No performance impact. The new mode is more lightweight on instanceswas lightening-fast on our test instances for 4 reasons: 1. We don’t make the user wait for the reindexation before displaying pages, since we put process everything in a queue and only 1 thread treats the queue. In our perf tests, it was lightening-fast compared to the version 1, but we’ll wait and get feedback from real-world cases. In the old system, if several users submitted pages, Requirement Yogi would make them wait until the page was reindexed, and it would also process all users at the same time, which meant several threads of Confluence could be kept busy with saving pages (That is, if you have hundreds of requirements per page and megabytes of data to save, 2. The queue means only 1 task is executed at any time, ensuring we don’t suddenly parse dozens of pages at the same time, 3. the reindex is much shorter due to the change of architecture, and 4. The algorithm itself is faster at parsing XML (but that may change depending on complexity).
When should you NOT switch to the new mode?
...