Hi, QueryParallelism only help in certain specific instances(queries with table scans and aggregations). Described more here: https://ignite.apache.org/docs/latest/SQL/sql-tuning#query-parallelism
The best way to speed up your query is to add appropriate indexes, and if you are using a cluster then collocate the data as appropriate. https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation https://ignite.apache.org/docs/latest/SQL/indexes Use the EXPLAIN statement to see e execution plan of a query https://ignite.apache.org/docs/latest/SQL/sql-tuning#using-the-explain-statement If you are preforming a distributed join(across multiple partitioned tables) follow this guide: https://ignite.apache.org/docs/latest/SQL/distributed-joins CPU utilization does not correlate one-to-one with query performance as other latencies, like disk, memory, etc.. come into play. You might also take a look at the LAZY flag to avoid waiting for all results to buffer before showing the output: https://ignite.apache.org/docs/latest/SQL/sql-tuning#lazy-loading See guide to SQL optimization here: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/sql-tuning Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
