Identifiying potential usecase for eager loading

[maxime-rainville]

We've recently implemented eager loading for Silverstripe CMS.

There are some scenarios in Silverstripe CMS where this could be useful. We should aim to identify a few high value one where this could be used to improve the responsiveness of the CMS and to validate the implementation of eager leading.

Acceptance criteria

• We've identified a few scenarios where we could try to use eager loading to speed up the CMS.
• For each scenario, we should aim to quantify the number of queries saved for a typical CMS site
• Cards are created as follow up.

Note

• The obvious scenario here is for relations GraphQL queries. That was the original impetus to get this created.
• There's likely somewhere this can be used either in the templating engine itself, or as a documented recommendation for when relations are used on the front-end
• Bear in mind that there are limitations to our current eager loading implementation
  • can only go up to 3 relations deep
  • eager-loaded relation lists are ArrayList rather than a subclass of DataList so it can't be used in some scenarios, e.g. we can't alter many_many_extrafields data, and we can't add items to the relation by adding to the list

Related

• Optimise SiteTree search when elemental is installed silverstripe-elemental#1067

[maxime-rainville]

Probably miss our window of opportunity on this one.