[MGNLADVCACHE-114] PersonalizedCachePolicy impacts performance due to interaction with JackRabbit Created: 11/Feb/21  Updated: 01/Feb/24

Status: Selected
Project: Advanced Cache
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: dx-core-6.3, performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-8246 Decoration impacts performance due to... Selected
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)
Documentation update required:
Yes
Epic Link: cache performance
Work Started:

 Description   

PersonalizedCachePolicy injects context provider and accesses the website workspace in order to account for page variants during caching, typically logging in as anonymous (in production end user scenarios).

Under heavy load this makes a lot concurrent users attempt to log in to JR via its user manager and blocking themselves (user manager uses a single synchronised session to manage log in credentials, see org.apache.jackrabbit.core.security.user.UserManagerImpl#session).

Using system context alleviates the issue somewhat (admin credentials are handled via shortcut), but later during interaction with the repo, we end up locking ourselves on some of its synchronised parts.

Can we optimise the policy so that it at least reduces/scales interactions with the repository?


Generated at Sun Feb 11 23:11:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.