...
YES. We don't recommend switching modes back-and-forth while creating baselines. When users create baselines, they create a snapshot of the requirements at a given time. If an administrator switches the mode, then requirements created in the next baseline will not be comparable with requirements in the previous baseline.
No performance impact. The new mode is more lightweight on instances, since we put 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).
When should you NOT switch to the new mode?
When you use requirements in the Scaffolding macro,
If you have many baselines and you want to compare requirements created before and after changing modes.
We’ll update this list if we are made aware of other anti-patterns.
Should an existing customer switch to the new mode?
...