[
https://issues.apache.org/jira/browse/IGNITE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Mashenkov updated IGNITE-4106:
-------------------------------------
Comment: was deleted
(was: I've noticed, that jdbc connection cached in ThreadLocal cache, one
connection per schema (ignite cache). It seems that public\system or may be
other pool's threads, that used to execute sql queries, hold connection objects.
If we will split queries in thread per partition manner, we can get
uncontrolled growth of opened connections. So, imho,
[IGNITE-4105|https://issues.apache.org/jira/browse/IGNITE-4105] should be done
at first.
)
> 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.6, 1.7
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Labels: performance
>
> 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)
