asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ian Maxon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ASTERIXDB-1077) Inverted index tests are slow compared to others
Date Thu, 20 Aug 2015 06:54:46 GMT

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

Ian Maxon commented on ASTERIXDB-1077:
--------------------------------------

As I understand it, the issue is more related to the fact all queries are point lookups rather
than range searches, like they are sometimes with the BTree/RTree. 

> Inverted index tests are slow compared to others
> ------------------------------------------------
>
>                 Key: ASTERIXDB-1077
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1077
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: Hyracks
>            Reporter: Ian Maxon
>            Assignee: Ian Maxon
>            Priority: Minor
>
> The inverted index tests take up the majority of the time spent in the Hyracks tests
(~25min out of 33min). Taewoo looked into this and discovered that the reason is at least
partially because of the parameters in AccessMethodTestsConfig . Those parameters are not
taking into account that queries on an inverted index will be far more expensive, because
they are all point lookups. It just uses roughly the same number of operations as the BTree/RTree
tests. 
> We may want to lower the number of operations, or perhaps there is some other performance
improvement that may ameliorate this situation. 



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

Mime
View raw message