[
https://issues.apache.org/jira/browse/OAK-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reopened OAK-1465:
------------------------------
reopening :)
this degradation is there also in 0.18-snapshot (double-checked..) - but with
much better overall figured, and slightly less dramatic:
{code}
# CreateManyIndexedNodesTest C min 10% 50% 90% max
N
Oak-Mongo 1 104 129 156 234 512
117
Oak-Mongo 1 107 130 163 224 277
119
Oak-Mongo 1 118 132 166 254 694
108
Oak-Mongo 1 118 146 178 247 961
101
Oak-Mongo 1 122 146 178 244 743
106
Oak-Mongo 1 125 147 185 242 402
105
Oak-Mongo 1 146 157 183 256 363
101
Oak-Mongo 1 140 160 192 249 1402
95
Oak-Mongo 1 152 163 195 264 545
95
Oak-Mongo 1 150 167 212 1563 4263
37
{code}
> 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
> 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.1.5#6160)
