[MGNLPN-625] Performance of info.magnolia.pages.app.browser.column.CachingVariantAwareTitleColumnDefinition Created: 11/Mar/22  Updated: 14/Mar/22  Resolved: 14/Mar/22

Status: Closed
Project: Magnolia Personalization
Component/s: Pages
Affects Version/s: 2.0.15
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Michiel Meeuwissen Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLPN-590 CLONE - Further Improve performance o... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

We have quite a lot of 'variants.'

 

 SELECT * FROM [mgnl:hasVariant] AS t
 
33031 nodes returned in 1461ms

 

 

I'm under the impression that this is more or less killing the entire usability of the pages app.

It is doing above query in `info.magnolia.pages.app.browser.column.CachingVariantAwareTitleColumnDefinition` quite often, and I think this is slowing everything down with multiple seconds. And it is probably also causing tremendous amounts of garbage.

 

 



 Comments   
Comment by Mercedes Iruela [ 14/Mar/22 ]

We already have MGNLPN-590 to improve this. Closed as duplicate.

Generated at Mon Feb 12 06:39:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.