[
https://issues.apache.org/jira/browse/IGNITE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830113#comment-15830113
]
ASF GitHub Bot commented on IGNITE-4106:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/1444
IGNITE-4106: SQL: parallelize sql queries over cache local partitions
Implemented
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-4106
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1444.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 #1444
----
commit 6fffa4afb6699fdb54fc5e3ca02797547c4d09ea
Author: Andrey V. Mashenkov <[email protected]>
Date: 2017-01-19T15:24:03Z
Implemented
----
> SQL: parallelize sql queries over cache local partitions
> --------------------------------------------------------
>
> Key: IGNITE-4106
> URL: https://issues.apache.org/jira/browse/IGNITE-4106
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 1.7
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Labels: performance
> Fix For: 1.9
>
> Attachments: 1node-4thread.jfr, 4node-1thread.jfr
>
>
> If we run SQL query on cache partitioned over several cluster nodes, it will
> be split into several queries running in parallel. But really we will have
> one thread per query on each node.
> So, for now, to improve SQL query performance we need to run more Ignite
> instances or split caches manually.
> It seems to be better to split local SQL queries over cache partitions, so we
> would be able to parallelize SQL query on every single node and utilize CPU
> more efficiently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
