[
https://issues.apache.org/jira/browse/OAK-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved OAK-2147.
---------------------------------
Resolution: Fixed
Assignee: Thomas Mueller
Closing it for now to not block the release unnecessarily.
[~amitj_76], I think your patch doesn't keep the (many) lanes in memory, so I
think this would be slightly better, but I don't know if the unit tests would
still work without change - is it OK if we keep it as it is right now? If not,
then let's open a new issue for the optimization.
> [Ordered Index] Indexing on large content is slow
> -------------------------------------------------
>
> Key: OAK-2147
> URL: https://issues.apache.org/jira/browse/OAK-2147
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Amit Jain
> Assignee: Thomas Mueller
> Fix For: 1.0.7, 1.1.1
>
> Attachments: OAK-2147-Amit.patch, OAK-2147-benchmark.txt,
> OAK-2147.patch
>
>
> Indexing large number of ordered properties is quite slow.
> Explore ways of making it faster. The current skip list implementation uses 4
> lanes with a probability of 10%. It should be made configurable and the
> defaults changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
