jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8185) Improve CompositeNodeStore performance
Date Tue, 02 Apr 2019 12:46:00 GMT

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

Marcel Reutegger commented on OAK-8185:
---------------------------------------

I think it would be good to configure the Oak-Composite-Store in a way that matches its intended
and recommended use. I would assume if performance is so much different with the current fixture,
then the setup is unlikely to be used that way.

> Improve CompositeNodeStore performance
> --------------------------------------
>
>                 Key: OAK-8185
>                 URL: https://issues.apache.org/jira/browse/OAK-8185
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: store-composite
>            Reporter: Marcel Reutegger
>            Assignee: Tomek Rękawek
>            Priority: Minor
>         Attachments: OAK-8185-update-fixture.patch, composite-node-builder.txt
>
>
> While working on OAK-8141 I noticed the benchmark numbers for GetDeepNodeTest on Oak-Composite-Store
are rather low compared to Oak-Segment-Tar.
> {noformat}
> Apache Jackrabbit Oak 1.12-SNAPSHOT
> # GetDeepNodeTest                  C     min     10%     50%     90%     max       N

> Oak-Segment-Tar                    1      35      37      39      41      64    1524
> Oak-Composite-Store                1     203     204     208     214     236     288
> {noformat}
> In an offline conversation [~tomek.rekawek] mentioned the overhead shouldn't be that
big because the implementation should switch to the non-composite implementation as soon as
the read operation traverses into the global/writable node store. It seems however, this is
not the case  when running GetDeepNodeTest. So, this may well be a bug and not an improvement,
as filed at the moment.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message