[
https://issues.apache.org/jira/browse/OAK-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175090#comment-15175090
]
Chetan Mehrotra edited comment on OAK-4076 at 3/2/16 7:16 AM:
--------------------------------------------------------------
[patch|^OAK-4076-v1.patch] which slightly modifies the {{PropertyIndex}} plan
calculation logic by moving the {{uuid}} to front (as first candidate) for uuid
queries. With this small change the benchmark does not show any difference with
increase in number of indexes
{noformat}
# UUIDLookupTest C min 10% 50% 90% max
N
Oak-Tar 1 2 2 3 3 26
21695 (50, query)
{noformat}
Given the uuid-> path query is so frequent and fired from within Oak code such
a special casing should be ok.
[~tmueller] Thoughts? Can we use this approach? If yes then I can open a new
issue and apply it
was (Author: chetanm):
[patch|^OAK-4076-v1.patch] which slightly modifies the {{PropertyIndex}} plan
calculation logic by moving the {{uuid}} to front (as first candidate) for uuid
queries. With this small change the benchmark does not show any difference with
increase in number of indexes
{noformat}
# UUIDLookupTest C min 10% 50% 90% max
N
Oak-Tar 1 2 2 3 3 26
21695 (50, query)
{noformat}
[~tmueller] Thoughts? Can we use this approach? If yes then I can open a new
issue and apply it
> 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
>
> Attachments: OAK-4076-v1.patch
>
>
> 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)
