Details
-
Epic
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
cache performance
-
Empty show more show less
Description
Context
See the notes from UHZ for pain points and initial findings
Questions for discovery
- (How) can we implement a cash flush policy that does not rely on observation?
- Can we rely on publication instead?
- UZH does this via the NavigationAwareCacheCleaner.java
, which uses a filter for intercepting publish requests instead of relying on observation like we do. Can we leverage this solution? - How does that affect eager re-caching?
- Can we do it in the background? Consistency guarantees?
Discover notes
- See on Notion
Checklists
Acceptance criteria
Attachments
Issue Links
- relates to
-
MAGNOLIA-9176 Apply central threadpool to DelayedExecutor
-
- Closed
-
-
MGNLCACHE-240 Optimise EhCache3Factory cache wrapping functionality
-
- Open
-
-
MGNLCACHE-241 Consider replacing ReentrantRWLocks with StampedLocks
-
- Open
-
-
MAGNOLIA-9056 Memory leak when re-registering module
-
- Selected
-
-
MGNLADVCACHE-124 Introduce new Flush policy and rely on completion of publish process to flush cache per site in 6.3
-
- Resolved
-
- links to
(1 links to)