You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2023/09/14 08:34:00 UTC

[jira] [Resolved] (IGNITE-19981) Calcite engine. Optimize mapping sending with query start request

     [ https://issues.apache.org/jira/browse/IGNITE-19981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov resolved IGNITE-19981.
----------------------------------------
    Resolution: Won't Fix

Looks like there is no performance boost after implementation. Benchmarks show reduced network usage, but increased CPU usage and lower overall throughput. 
 

> Calcite engine. Optimize mapping sending with query start request
> -----------------------------------------------------------------
>
>                 Key: IGNITE-19981
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19981
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksey Plekhanov
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: ise
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Currently we send the whole fragment mapping with query start request to each node, but on the node we need only local mapping (we need only set of partition to process by current node). If there are a lot of nodes and a lot of partitions - mapping can take a lot of space 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)