Hi, There is no documentation per se which states whether/how many objects are allocated in memory as this varies as new builds/versions are released. That being said, you can control the load/throughput/memory/enabled feature set/etc.., and therefore manage object allocation indirectly. For example, you have the option of turning metrics on or off for specific caches or data regions.
see: https://apacheignite.readme.io/docs/cache-metrics#enabling-cache-metrics and: https://apacheignite.readme.io/docs/memory-metrics This would change the number/frequency of metric related discovery messages you mentioned. There are also a variety of optimizations you could make to make Ignite perform faster see: https://apacheignite.readme.io/docs/jvm-and-system-tuning https://apacheignite.readme.io/docs/durable-memory-tuning https://apacheignite.readme.io/docs/performance-tips https://apacheignite.readme.io/docs/preparing-for-production Here you are able to set the various memory and persistence related parameters used by Ignite, and thereby tune your app to your use-case. If you concerned w/object allocation, the best advice is to look into various high performance garbage collectors available like shenandoah(https://wiki.openjdk.java.net/display/shenandoah/Main) and Azul. See this blog post describing how Ignite and Azul Zing JVM are used together to power low-latency use cases: https://www.azul.com/igniting-in-memory-performance-with-gridgain-and-zing/ Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
