You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by "ilya.kasnacheev" <il...@gmail.com> on 2018/06/09 14:37:41 UTC

Re: Heap exhaustion when querying

Hello!

Sorry for the late reply! I think the good description of this flag is found
in JDBC driver's documentation.

https://apacheignite-sql.readme.io/docs/jdbc-driver#section-parameters

lazy

Lazy query execution.

By default, Ignite attempts to fetch the whole query result set to memory
and send it to the client. For small and medium result sets, this provides
optimal performance and minimize duration of internal database locks, thus
increasing concurrency.

However, if the result set is too big to fit in the available memory, then
it can lead to excessive GC pauses and even OutOfMemoryError. Use this flag
as a hint for Ignite to fetch the result set lazily, thus minimizing memory
consumption at the cost of moderate performance hit.

More on the concept of lazy evaluation:
https://en.wikipedia.org/wiki/Lazy_evaluation

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/