There are some interesting results after applying query execution improvements for MGNLPER-190. It can be seen at this Notion document:
https://www.notion.so/magnoliacms/Monitoring-and-tracking-metrics-d6c3037f7a584aa79911ecaf3d3bd22f

The interesting part to investigate is how is possible to achieve such a great improvement in Assets big-data repository but not at Pages big-data repository. It may be interesting to investigate some possible reasons:

• What is that so different from Assets repository and Pages repository?
  • Pages are more hierarchical, Assets have a more flat structure
  • https://docs.magnolia-cms.com/paas/best-practices/structuring-jcr-workspace.html
  • Is the JCR tree structure very heavy for this search purpose?
• Why the system gets blocked after performing some search?
  • todo clarify this 
  • not an issue with the current changes

5 dev days for spike, Thurs 1st June for end date