You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Bikramjeet Vig (JIRA)" <ji...@apache.org> on 2018/03/07 20:19:00 UTC
[jira] [Created] (IMPALA-6621) Improve In-predicate performance by
using an alternative data structure for checking set membership
Bikramjeet Vig created IMPALA-6621:
--------------------------------------
Summary: Improve In-predicate performance by using an alternative data structure for checking set membership
Key: IMPALA-6621
URL: https://issues.apache.org/jira/browse/IMPALA-6621
Project: IMPALA
Issue Type: Improvement
Components: Backend
Affects Versions: Impala 2.13.0
Reporter: Bikramjeet Vig
Assignee: Bikramjeet Vig
Attachments: release_build_BoostFlatset.txt.txt, release_build_BoostUnorderedset.txt.txt, release_build_StdSet.txt.txt
Currently when using a SET_LOOKUP strategy for in-predicates in impala we use an std:set object for checking membership.
Using other data structures like boost::unordere[^release_build_BoostFlatset.txt.txt]d_set and boost::flat_set we can get a significant performance improvement. Please see attached results of micro benchmarks using std::set, flat_Set, unordered_set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)