[
https://issues.apache.org/jira/browse/OAK-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545885#comment-17545885
]
Thomas Mueller commented on OAK-9780:
-------------------------------------
Some statistics:
{noformat}
Document-Documents
MaxTotalWeight local 42 M / remote 171 M (0.67 hit rate)
AverageLoadPenalty local 56 / remote 1'287 (!)
LoadCount local 759'784 / remote 13'781'775
TotalLoadTime local 44'010'968 / remote 17'739'526'349
Document-NodeState
MaxTotalWeight local 93 M / remote 375 M (0.98 hit rate)
AverageLoadPenalty local 96'320 / remote 166'047 (!)
LoadCount local 688'766 / remote 90'841'823
TotalLoadTime local 66'342'523'353 / remote 15'084'040'260'590
PersistentCache.NodeCache.diff: local+remote
PersistentCache.NodeCache.local_diff: local+remote
PersistentCache.NodeCache.children: local only (!)
PersistentCache.NodeCache.node: local only (!)
PersistentCache.NodeCache.prev_document: local only (!)
{noformat}
It seems the remote MongoDB case is quite different from the local installation
(wrt performance); also, persistent cache configuration is very different. I
didn't take this into account yet in my simple test.
> PoC for DocumentNodeStore cache warming
> ---------------------------------------
>
> Key: OAK-9780
> URL: https://issues.apache.org/jira/browse/OAK-9780
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: documentmk
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Major
>
> Proof of concept of cache warming for DocumentNodeStore. Goal is for indexing
> to warm up the cache for a select few eg paths to allow for faster
> iterating/reading of the same eg paths later on
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
