ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexei Scherbakov <alexey.scherbak...@gmail.com>
Subject Re: Unexpected performance issue with SQL query followed by error
Date Thu, 02 Jun 2016 11:54:16 GMT
No, I think you wouldn't get increase for this particular query, because it
contains big result set,
which has to be downloaded to client over network.
But you can split the task between multiple nodes, run every job locally
and get result faster.
To achive what you can use affinity collocation [1]
What are you planning to do with the query result ?

[1] https://apacheignite.readme.io/docs/affinity-collocation

2016-06-02 9:23 GMT+03:00 jan.swaelens <jan.swaelens@sofico.be>:

> I see what you are saying, so if I would start lets say 4 nodes on the
> machine instead of 1 I should get a drastic increase of response time? I'd
> be happy to give that a try, anything special I need to cater for based on
> the case we are running here?
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726p5368.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Best regards,
Alexei Scherbakov

View raw message