[
https://issues.apache.org/jira/browse/OAK-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944984#comment-13944984
]
Marcel Reutegger commented on OAK-1465:
---------------------------------------
I ran Stefan's test on my machine and I see a very steep increase in max time
to execute a test loop. The time is roughly equal to the time it takes mongodb
to flush the mmap files. It does it once every minute, which means each test
iteration sees one flush event. Over time the flush takes up to 20 seconds on
my machine. MongoDB was running on a regular hard disk drive. I will re-run the
test on an SSD...
> 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)
