Finding translations for documents / folders is inefficient and costly

The available translations for a node for every cms user and site user are the same nodes. The only difference is whether the user session can read the translation or not.

In the CMS now every logged in user finds out itself which translations there are of a folder or document : It does so by a query, PER folder or document.

This means, a folder with 50 documents in it, results in 50 separate queries to find out the translations....every time the folder is clicked.

Although the queries are really fast, with more than 100 logged in CMS users it is reported to become a BIG congestion point in Lucene with many threads being blocked by IO.

Obviously, translations can (and SHOULD) be served by a service backed by just one system session which caches results and invalidates them when needed. This way, the CMS UI won't impact performance so much when many users are logged in. Also the HST can use this service for optimization purposes