[OAK-2646] Look for alternative cache invalidation logic for better performance

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Done
• Component/s: mongomk
• Labels: performance
• Assignee: Unassigned
• Reporter: Chetan Mehrotra
• Created: 18/Mar/15 04:45
• Updated: 08/Oct/19 15:21
• Resolved: 01/Jul/15 13:26

Description

Current cache invalidation logic has a higher cost. For e.g. in one of the deployment following log was seen

12.03.2015 09:24:25.579 *INFO* [DocumentNodeStore background thread] org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore Background operations stats (clean:0, split:0, write:0, read:11848 ReadStats{cacheStats:InvalidationResult{invalidationCount=4, upToDateCount=286761, cacheSize=300411, timeTaken=10589, queryCount=654, cacheEntriesProcessedCount=138633}, head:1, cache:11842, dispatch:5, purge:0}

Issue Links

• is related to: OAK-1328 refactor DocumentMK caching
• is related to: OAK-2792 Investigate feasibility/advantages of log-tailing mongo op-log to invalidate cache
• is related to: OAK-2793 Time limit for HierarchicalInvalidator
• relates to: OAK-3002 Optimize docCache and docChildrenCache invalidation by filtering using journal
• relates to: OAK-2187 Document cache invalidation logic generating lots of garbage