[MGNLPER-191] Investigate the query time results for Pages in Big Data scenario Created: 05/May/23  Updated: 25/Jul/23  Resolved: 12/Jun/23

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Spike Priority: Neutral
Reporter: Andrei Ichimescu Assignee: ricardo gonzalez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLPER-190 Find and document opportunities to im... Open
Relates
relates to MGNLPER-168 JcrSearchResultSupplier generates ine... Closed
Template:
Date of First Response:
Epic Link: [JCR] Search Performance issues
Team: AuthorX
Work Started:

 Description   

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:

 

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


Generated at Mon Feb 12 10:29:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.