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] [Comment Edited] (OAK-5222) Optimize the multiplexing node store
Date Tue, 20 Dec 2016 10:04:58 GMT

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

Tomek Rękawek edited comment on OAK-5222 at 12/20/16 10:04 AM:
---------------------------------------------------------------

New oak-run fixtured added to trunk in [r1772622|https://svn.apache.org/r1772622], [r1775244|https://svn.apache.org/r1775244].


was (Author: tomek.rekawek):
New oak-run fixtured added to trunk in [r1772622|https://svn.apache.org/r1772622].

> 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.8
>
>
> 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