[ https://issues.apache.org/jira/browse/IGNITE-14816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398142#comment-17398142 ]
Aleksey Plekhanov commented on IGNITE-14816: -------------------------------------------- [~tledkov-gridgain], in most cases it will give a performance boost. I see only one disadvantage here: the use of RuntimeSortedIndex with almost unique values. In the case of correlated NL join with unique RuntimeSortedIndex as the right input, for example, we will do 2 times more comparisons for each row of the left input. > Calcite engine. Change TreeMap in sorted IndexSpoolNode to ArrayList > -------------------------------------------------------------------- > > Key: IGNITE-14816 > URL: https://issues.apache.org/jira/browse/IGNITE-14816 > Project: Ignite > Issue Type: Improvement > Reporter: Aleksey Plekhanov > Assignee: Pavel Pereslegin > Priority: Minor > Labels: calcite3-required > Time Spent: 50m > Remaining Estimate: 0h > > {{IgniteSortedIndexSpool}} assumes that the underlying input is already > sorted, but the execution node creates {{TreeMap}} to find the rows (see > {{IndexSpoolNode#createTreeSpool}}). This {{TreeMap}} can be replaced with > {{ArrayList}} and binary search with the same efficiency for searching and > lower costs for inserting data. > -- This message was sent by Atlassian Jira (v8.3.4#803005)