You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/01/19 09:26:00 UTC

[jira] [Assigned] (IGNITE-18580) Sql. Redesign the Exchange to use a pull-based approach

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

Konstantin Orlov reassigned IGNITE-18580:
-----------------------------------------

    Assignee: Konstantin Orlov

> Sql. Redesign the Exchange to use a pull-based approach
> -------------------------------------------------------
>
>                 Key: IGNITE-18580
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18580
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> Currently, Exchange uses push-based strategy to exchange batches between different fragments. Such an approach works well for cases of scanning the whole table, but may cause an unnecessary overhead in cases, where the smaller amount of rows is expected. For example, for query "SELECT * FROM table LIMIT 4", IO_BATCH_SIZE * IO_BATCH_COUNT * NODE_COUNT rows will be sent over network in push-based approach, whereas only 4 * NODE_COUNT will be sent in pull-based.
> Let's redesign Exchange to gain more control over amount of data that is sent over the network. 



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