Hello! I guess that you have EVT_NODE_METRICS_UPDATED event enabled on client nodes (but maybe not on server nodes)
It will indeed produce a lot of garbage so I recommend disabling the recording of this event by calling ignite.events().disableLocal(EVT_NODE_METRICS_UPDATED); + dev@ Why do we record EVT_NODE_METRICS_UPDATED by default? Sounds like a bad idea yet we enable recording of all internal events in GridEventStorageManager. -- Ilya Kasnacheev пн, 26 окт. 2020 г. в 19:37, ssansoy <s.san...@cmcmarkets.com>: > Hi, here's an example (using YourKit rather than JFR). > > Apologies, I had to obfuscate some of the company specific information. > This > shows a window of about 10 seconds of allocations > > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2797/MetricsUpdated.png> > > > Looks like these come from GridDiscoveryManager - creating a new string > every time. This happens several times per second it seems. Some of these > mention other client nodes - so some other production app in our firm, that > uses the cluster, has an impact on a different production app. Is there any > way to turn this off? Each of our clients need to be isolated such that > other client apps do not interfere in any way > > Also > > < > http://apache-ignite-users.70518.x6.nabble.com/file/t2797/TcpDiscoveryClientMetricsUpdateMessage.png> > > > These update messages seem to come in even though metricsEnabled is turned > off on the client (not specificied). > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
