[
https://issues.apache.org/jira/browse/IGNITE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304488#comment-16304488
]
ASF GitHub Bot commented on IGNITE-6022:
----------------------------------------
GitHub user dolphin1414 opened a pull request:
https://github.com/apache/ignite/pull/3298
IGNITE-6022: Implemented native batch execution support for DML statements.
Implemented native batch execution support for DML statements.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6022
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3298.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3298
----
commit eacd01fc01c9dea0b81e7aec8d5bbd89852401ae
Author: rkondakov <rkondakov@...>
Date: 2017-12-27T11:53:30Z
IGNITE-6022: Implemented native batch execution support for DML statements.
----
> 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)
