Hi Shane, Your understanding is right. During the query execution Ignite copies cache entries into the heap memory.
Java heap size depends on the SQL queries you perform. If the query fetches a lot of data it makes sense to increase the max size of the heap. If the queries use "order by", "group by" or joins then I would recommend creating indexes to avoid loading all rows of the table into the heap memory. Also, it is possible to restrict a number of concurrent SQL queries by configuring a thread pool size https://apacheignite.readme.io/docs/thread-pools#section-queries-pool Best Regards, Roman -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
