jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4076) Benchmark to measure affect of number of indexes on query performance
Date Tue, 01 Mar 2016 09:25:18 GMT

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

Chetan Mehrotra commented on OAK-4076:
--------------------------------------

Benchmark result

{noformat}
# UUIDLookupTest                   C     min     10%     50%     90%     max       N
Oak-Tar                            1       3       3       4       6      36   14156 (5, Session#getNodeByIdentifier)
Oak-Tar                            1       7       8       8      11     148    6759 (50,
Session#getNodeByIdentifier)
Oak-Tar                            1       2       2       3       4     122   20532 (5, query)
Oak-Tar                            1       4       5       5       7     243   10892 (50,
query)
{noformat}

Points to draw
* Increase in number of index config nodes causes loss in throughput. For e.g. above changing
the no of indexes from 5 yo 50 leads to ~50% degradation
* Somehow {{Session#getNodeByIdentifier}} is 50% slower compared to query. This I am not sure
why its slow

> Benchmark to measure affect of number of indexes on query performance
> ---------------------------------------------------------------------
>
>                 Key: OAK-4076
>                 URL: https://issues.apache.org/jira/browse/OAK-4076
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: run
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.6
>
>
> This is related to OAK-1273. I would like to have a benchmark to see how increase in
number of indexes affect uuid lookup. Currently uuid lookup relies on query so the trend would
be similar for other queries



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

Mime
View raw message