[
https://issues.apache.org/jira/browse/OAK-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945121#comment-13945121
]
Marcel Reutegger commented on OAK-1465:
---------------------------------------
The test run on the SSD (although already 4 years old), shows a similar
behavior. After a while the MongoDB mmap flushing affects the test, but it
seems to settle at roughly 18 seconds per flush. I'll have to run a longer test
to see if it goes further up.
I did notice a minor issue in {{NodeDocument.getNewestRevision()}} where the
cost increases slightly when the revision history gets bigger. Though, the
effect of the mmap flushing is much more significant.
> performance degradation with growing index size on Oak-Mongo
> ------------------------------------------------------------
>
> Key: OAK-1465
> URL: https://issues.apache.org/jira/browse/OAK-1465
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Affects Versions: 0.17.1
> Reporter: Stefan Egli
> Assignee: Marcel Reutegger
> Priority: Blocker
> Fix For: 0.20
>
> Attachments: CreateManyIndexedNodesTest.java
>
>
> Tested with an oak-snapshot of Monday Feb 24, 10AM EST.
> Noticed that when the amount of nodes indexed - eg wrt a particular property
> - the adding of nodes becomes slower and slower.
> Will attach a oak-run benchmark to underline this. Basically the scenario
> where this occurred was:
> * have a number of "level 1" nodes (eg 100)
> * under those "level 1" nodes, add a growing list of children, each with a
> property that is indexed (ie that index is actually growing and is probably
> causing the slowdown).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
