Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-28143

getPermissionCriterion() should be cached per user

    XMLWordPrintable

Details

    Description

      The customer experienced huge load and long execution time using SearchService for content with many states.

      For every element, SearchService has to check if a content has the correct state (to be displayed for e.g.). In this particular situation, the customer has at least 19 defined states and tries to perform search for 50 elements. For each of them, SearchService iterates over every state and check it. This operation is very expensive. It will be good to cache getPermissionCriterion() result per user. This way, we will avoid repeating this expensive permission checking in every iteration.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              kamil.madejski@ibexa.co Kamil Madejski
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: