Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-1999

Performance: versioning sub-engine: org.jahia.services.lock.LockRegistry.isAcquireable to move in the AJAX sitemap

Details

    • Bug
    • Resolution: Done
    • Critical
    • WCM 5.0 SP2
    • WCM 5.0 SP2
    • None
    • Sp217448

    Description

      Tested on the imported online demo.

      If I enter the verisoning sub-engine (page properties from the home page), it directly try to put a lock on the whole site (before even having selected the choice of restoration or the pages to restore). Such a check is very time consuming (cf JAMON performance in screesnhot for a small site of 40 pages -to be tested on a large site of 10'000 pages).

      So could we only acquire locks when displaying the AJAX sitemap and only for the selected pages (and perhaps the sub-page. I do not know how the versioning module works and if the non-selected sub-pages could be destroed or modified by a parent page modifications). But most of the time we do not need to lock the full site as we will only restore one section (e.g. the home page and one section below the home, but not all sections).

      I also entered another JIRA in order to try to AJAX such locks as this also cause some display problem in the workflow sitemap (very slow).

      TestRail: Results

        Attachments

          Issue Links

            Activity

              [JAHIA-1999] Performance: versioning sub-engine: org.jahia.services.lock.LockRegistry.isAcquireable to move in the AJAX sitemap

              Discussed in pm-dm (https://jahia.slack.com/archives/CNRFEDYHX/p1728046393480479), closing, as Inactive, all issues that were last updated before January 2023 (22 months ago).
              Please re-open if necessary

              fgerthoffert@jahia.com Francois Gerthoffert added a comment - Discussed in pm-dm ( https://jahia.slack.com/archives/CNRFEDYHX/p1728046393480479 ), closing, as Inactive, all issues that were last updated before January 2023 (22 months ago). Please re-open if necessary

              already fixed for SP2

              khue Khue N'Guyen (Inactive) added a comment - already fixed for SP2

              I also do not understand why the getLanguagesState command is called over and over and is not stored in cache. For instance, in the JAMon example, I just went into the versioning tab once. Then I left the versioning tab to go into the import tab, flush jamon, and went again in the versioning tab, the GetLanguageStates method is called again with approximately the same time (5.5 sec for 40 pages), why? Everthing should be in cache isn-t'it?

              scroisier Stephane Croisier (Inactive) added a comment - I also do not understand why the getLanguagesState command is called over and over and is not stored in cache. For instance, in the JAMon example, I just went into the versioning tab once. Then I left the versioning tab to go into the import tab, flush jamon, and went again in the versioning tab, the GetLanguageStates method is called again with approximately the same time (5.5 sec for 40 pages), why? Everthing should be in cache isn-t'it?

              People

                khue Khue N'Guyen (Inactive)
                scroisier Stephane Croisier (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases

                      Packages

                        Version Package
                        WCM 5.0 SP2