[
https://issues.apache.org/jira/browse/IGNITE-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-2368.
-------------------------------------
Resolution: Won't Fix
Closing as "won't fix" for two reasons:
1) It doesn't scale because only one machine will perform query execution.
2) It can generate considerable overload on a server. Instead, it is preferable
to perform reduce on client to minimize risks for server nodes.
> Performance optimization for an IgnitCache.query execution.
> -----------------------------------------------------------
>
> Key: IGNITE-2368
> URL: https://issues.apache.org/jira/browse/IGNITE-2368
> Project: Ignite
> Issue Type: Improvement
> Components: SQL
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ershov
> Assignee: Vladimir Ozerov
> Labels: performance
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Current solution of an sql query executed from client node for replicated
> cache could be improved.
> As for now we split initial query into map and reduce steps on a client
> node, but it would be more effective just to send initial query to a data
> node and execute it there without splitting since cache is replicated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
