SP2 Performance on versioning tab: 20 minutes that my engine is running on 10'000 pages DB - still no result - please put a please wiating logo at least

I tried to open the versioning tab on the home page (home properties) of the 10'000 pages DB. I am waiting for 20 minutes and after 20 minutes FF automatically closes my pop-up window (great!). But the process is still running on the back-end! My PG and Java uses nearly 100% of my CPU and I have no load on the server (I am alone logued as root).

So such requests should be definitively prohibited in Jahia. We should always find algorithm which allow a classical user to at least navigate without too much performance issues within the engines. Moreover the engine becomes fully blank. You even do not have a "please wait in progress" logo or something like that. What if now 20 editors, playing with the system, clcik on the versioning tab on a 10'000 pages sites (very probable scenario)?

If I take a look into Jamon all the time is spent on calculating the workflow:states (definitively we need to improve such damn workflowstate) and on LockRegistry.isAcquireable. What I do not understand is why we need to acquire all these locks at this stage of the process. Perhaps the user only wants to check for an archive but do not want to restore anything. What if he only wants to restore a single section of one page in the topbar and launched the versioning from the home page just to select one single page? So we should defintively only lock and calculate workflow state only when expanding the sitemap in the versioning (or even better only when the user select some pages to restore - cf parent jira).