Lazy is something which we can use when we are expecting huge result set to minimize the memory consumption at the cost of little performance hit. However my requirement to run a query by joining couple of tables with complex where clause to debug some data related issues, this query may not return huge result set, but scan the the complete table to get the result set, during this time it should not hit the performance.
So my question here is, can we try applying the same feature like eviction, in case of eviction, if the record is not there in RAM, it will go to backing store and gets the data and also load it to memory. Similar way, can we hint the cluster to run the query on backing store instead of RAM, so that that the impact on RAM would be less if you are running the query on backing store. In our case, we have 2 TB servers with 128 core machine, very high end machines, RAM is utilized upto 60 to 70%, however CPU resources are not utilized. Hope I was able to convey my adhoc requirements to run various SQL queries to debug data related issues and consequences of these queries on the performance on the cluster Thanks Naveen -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
