[MAGNOLIA-6776] Implement mixin mgnl:hasVersion to avoid excessive access to the version store Created: 16/Sep/16  Updated: 10/Aug/17  Resolved: 08/Oct/16

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 5.5

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLUI-3972 Avoid excessive access to the version... Closed
causality
is causing MAGNOLIA-7004 Restoring the first version of any no... Closed
dependency
depends upon MAGNOLIA-6774 Same uuids in multiple workspaces lea... Closed
is depended upon by MGNLUI-3972 Avoid excessive access to the version... 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)
Sprint: Kromeriz 65
Story Points: 2

 Description   

Each click on an elements in content apps leads to requests to the version store. This can be expensive especially for big installations. I have not tracked it down but my guess would be that it is a availability test for an action which checks wether the node has versions or not.

To verify this one can enable derby logging like described here: http://magnolia-experts.com/monitoring-queries-to-the-derby-database/

Attention: jackrabbit caches nodes in memory (16MB bei default) so with a small installation like the demo project the queries will be only executed during the first access and not by follow up browsing.

EDIT:
https://wiki.magnolia-cms.com/display/DEV/Concept+-+New+mixin+to+avoid+excessive+access+to+the+version+store+while+browsing+content


Generated at Mon Feb 12 04:17:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.