Hi we can't use the thin client unfortunately because we rely heavily on
continuous queries to notify clients when an update has occurred without
delay.

based on the heap dump above, is there anything we can do to get around this
large mem footpring on the client? It seems odd that the client needs
metadata stored on it locally for all 50 caches for example, even though the
client is only ever interested in one of them for example



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

Reply via email to