jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-5222) Optimize the multiplexing node store
Date Mon, 05 Dec 2016 13:33:58 GMT

    [ https://issues.apache.org/jira/browse/OAK-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722271#comment-15722271
] 

Tomek Rękawek commented on OAK-5222:
------------------------------------

I realised that the multiplexing fixture itself is not optimal, as it should register multiple
paths within a mount. We probably should have two parameters: one for #mounts and the second
for #paths-per-mount.

I'll try to fix it and come back with the results.

> Optimize the multiplexing node store
> ------------------------------------
>
>                 Key: OAK-5222
>                 URL: https://issues.apache.org/jira/browse/OAK-5222
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>             Fix For: 1.6
>
>
> I added support for the multiplexing node store for the oak-run benchmark fixtures. It
seems that the performance in ReadDeepTreeTest is linearly dependent on the mount counts:
> {noformat}
> Mounts	N
> 0	729
> 1	402
> 2	287
> 3	209
> 4	188
> 5	154
> 6	133
> 7	126
> 8	104
> 9	100
> 10	85
> 20	46
> {noformat}
> {{N}} - throughput in 60 seconds. Following command was used:
> {noformat}
> $ java -jar target/oak-run-1.6-SNAPSHOT.jar benchmark ReadDeepTreeTest Oak-Multiplexing
--mounts=10
> {noformat}
> It should be possible to improve this, so we won't have a noticeable performance decrease
for 1000 mounts.
> //cc: [~rombert]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message