[
https://issues.apache.org/jira/browse/ASTERIXDB-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746490#comment-14746490
]
Taewoo Kim commented on ASTERIXDB-1077:
---------------------------------------
Basically, we have too many searches per each insert, delete, or search test.
For each search modifier, we conduct 400 searches. Thus, if we have three
search modifier in each test, then we conduct 1,200 searches. For example,
LSMInvertedIndexSearchTest takes about two minutes and it conducts 11,200
searches. We need to reduce the number of tests. Chen and I will analyze this
further.
> 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: Chen Li
> 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)
