Re: Client App Object Allocation Rate

Hi did you get a response for this out of interest? also is there a ticket we can follow? We really need to understand this - and ideally turn it off -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

Hello! Good question. Did something at all change after you set it? I'm not sure why the message is so large in your cases, it's tens of kb. Regards, -- Ilya Kasnacheev вт, 10 нояб. 2020 г. в 20:27, ssansoy : > Yep theyre the ones we'd like to turn off... is that possible with >

Re: Client App Object Allocation Rate

Yep theyre the ones we'd like to turn off... is that possible with IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=true? it doesn't seem to have an effect -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

Hello! Yes, it's not cache statistics but node statistics (org.apache.ignite.cluster.ClusterMetrics) Regards, -- Ilya Kasnacheev пн, 9 нояб. 2020 г. в 21:09, ssansoy : > Also according to the heap dump they aren't cache statistic messages, but > rather, TcpDiscoveryClientMetricsUpdateMessage

Re: Client App Object Allocation Rate

Also according to the heap dump they aren't cache statistic messages, but rather, TcpDiscoveryClientMetricsUpdateMessage -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

hi, 6k/sec was a misreading on my part - its more 1mb+ ! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

Hello! I'm actually not convinced that 6k/sec is a lot. Metrics update messages are passed between nodes to calculate cluster-wide cache metrics. Have you tried turning them off by setting *IGNITE*_*DISCOVERY*_*DISABLE* _CACHE_*METRICS*_UPDATE=true, in form of system property or env var?

Re: Client App Object Allocation Rate

Hi was there any update on this? thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

Thanks, please do keep us posted - perhaps with a ticket number or something we can track as this is currently a blocker for putting ignite into production. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

Hello! Okay, that's not very cool. I hope to get some response from development side at this point. Sans reaction, I will file a ticket. Regards, -- Ilya Kasnacheev пн, 2 нояб. 2020 г. в 15:03, ssansoy : > Apologies I may have spoken to soon (I was looking at the wrong process). > > It

Re: Client App Object Allocation Rate

Apologies I may have spoken to soon (I was looking at the wrong process). It looks like we can't turn EVT_NODE_METRICS_UPDATED off as it is designated as an internal event GridEventStorageManager.disableEvents line 441 (ignite 2.8.1), this checks to see if the event that is being disabled is

Re: Client App Object Allocation Rate

That's great! seems to eliminate a lot of the traffic. Are there any other optimizations like this you know of that we can make to reduce this any further? We also have the issue documented in this thread:

Re: Client App Object Allocation Rate

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

Re: Client App Object Allocation Rate

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 Looks like these come from

Re: Client App Object Allocation Rate

Hello! Can you please run your app with JFR configured to record object allocation, to see where it actually happens, and share some results? Thanks, -- Ilya Kasnacheev пт, 23 окт. 2020 г. в 17:40, ssansoy : > This doesn't seem to help unfortunately. > Re-examining the allocation stats, it

Re: Client App Object Allocation Rate

This doesn't seem to help unfortunately. Re-examining the allocation stats, it seems the app is actually allocating around 1.5mb per second with ignite (vs only 0.15mb per second without ignite in the app). I've read about past issues with IGNITE_EXCHANGE_HISTORY_SIZE causing a lot of allocations,

Re: Client App Object Allocation Rate

Thanks! I will have a read through -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Client App Object Allocation Rate

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

Client App Object Allocation Rate

Hi, we are moving away from a legacy (in house) distributed cache solution to ignite, and are doing some profiling of new app vs old app behaviour before we go live. One thing we have noticed, is that the object allocation rate is higher in the version of the app running with the ignite client