XMLWordPrintable

    Details

      Description

      eZ Publish 5.x / eZ Platform might (query optimizers add some weight as well) benefit from getting a Query optimizer.

      The point has been brought up a few times and most recently by Felix Woldt as one way of improving issue brought up in recent blog post SearchService Performance.

      The ideas are several:

      • optimize identifier criterias to transfer them to using the id equalent ( ContentTypeIdentifier -> ContentTypeId )
      • optimize away uneeded permission checks
        • 1. detect root level criteria for Location, Subtree and Section in user query and skip role assignments with limitations that does not match
        • 2. detect root level criteria for Location, Subtree, Section, ContentType in user query and skip policies which has limitations that does not match

      However as hinted in the intro, there is a cost to this, so it might only make sense to do when Query's are persisted (ref "Views" as they are called in REST API v2).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              andre.romcke@ez.no André Rømcke
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: