Yes, this is correct, but this is not a performance issue, this is a performance gain.
Your data set is split across the nodes and the indexes are also split in the same way. So, if you have 100GB of data and 10 nodes, then each node will end up with about 10GB of data. In this case, Ignite will execute the query across 10 nodes in parallel and each query will execute on 1/10 of the data. Quite often this results in almost linear performance gain. On Mon, Jan 25, 2016 at 8:59 AM, Sergi Vladykin <[email protected]> wrote: > Correct. > > Sergi > > 2016-01-25 18:39 GMT+03:00 Andrey Nestrogaev <[email protected]>: > >> Hi All, >> >> Is any sql query, executed with partitioned cache, will always be executed >> on every node where cache is deployed, irrespectively which predicates are >> used or what indexes are created? >> >> >> >> -- >> View this message in context: >> http://apache-ignite-users.70518.x6.nabble.com/Sql-query-performance-with-partitioned-caches-tp2700.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
