ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Kondakov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6022) SQL: add native batch execution support for DML statements
Date Tue, 09 Jan 2018 17:51:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318810#comment-16318810
] 

Roman Kondakov commented on IGNITE-6022:
----------------------------------------

[~vozerov], [tests|https://ci.ignite.apache.org/viewLog.html?buildId=1030080&] are ok,
please review.

> SQL: add native batch execution support for DML statements
> ----------------------------------------------------------
>
>                 Key: IGNITE-6022
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6022
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.1
>            Reporter: Vladimir Ozerov
>            Assignee: Roman Kondakov
>              Labels: iep-1, performance
>             Fix For: 2.4
>
>
> We have batch execution support for JDBC and ODBC drivers. This decreases number of network
hops. However, we do not have any batch execution support on the server side. It means that
for batch of N similar statements, every statement will go through the whole execution chain
- parsing, splitting, communication with servers. And while parsing and splitting might be
avoided with help of statement cache, the most heavy part - network communication - is still
there.
> We need to investigate how to optimize the flow for batch updates. Possible improvements:
> 1) Execute statements with certain degree of parallelism;
> 2) Send several query execution requests to the server at once;
> 3) Ensure that caches are used properly for batching - we should not parse the same request
multiple times.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message