Hi Val, We do create lots of object. I am getting 1M data points event minute. For data affinity, I create a key object for each data point. As I mentioned earlier I have two stages of processing. We create new key on both stages. So, creating close to 2M new keys every minute. I have changed that and running the test now.
Also If I understand correctly then when I do get() on cache, it creates a copy of the object and return that copy. Do you think turning off that behavior will help? Thanks, Biren On 8/23/17, 5:51 PM, "vkulichenko" <[email protected]> wrote: Biren, I see the jump and I actually see GC pauses as well (the longest one is the last line in log_2.txt). BTW, I don't think there is an quick jump, GC pause most likely blocks the monitor thread as well, so it just looks like a jump. Apparently, all these 30 seconds were spent in GC, and I'm pretty sure this is causing the issue. It looks like you're doing something that generates too many objects. My suggestion would be to use JFR [1] to profile object allocations and check what's going on. [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__apacheignite.readme.io_docs_jvm-2Dand-2Dsystem-2Dtuning-23section-2Dflightrecorder-2Dsettings&d=DwICAg&c=Zok6nrOF6Fe0JtVEqKh3FEeUbToa1PtNBZf6G01cvEQ&r=rbkF1xy5tYmkV8VMdTRVaIVhaXCNGxmyTB5plfGtWuY&m=LiHHncH7191OkF4vZnSdvf7qmC9q13uRiNImGL2Grwk&s=Vr1gZsnAesfDJTrXQDi-tphsPD3lQ1NL8q4Q7l1y70E&e= It is allowed to use cache API from receiver. To remove entry using streamer, you can use removeData() method. -Val -- View this message in context: https://urldefense.proofpoint.com/v2/url?u=http-3A__apache-2Dignite-2Dusers.70518.x6.nabble.com_Cluster-2Dsegmentation-2Dtp16314p16388.html&d=DwICAg&c=Zok6nrOF6Fe0JtVEqKh3FEeUbToa1PtNBZf6G01cvEQ&r=rbkF1xy5tYmkV8VMdTRVaIVhaXCNGxmyTB5plfGtWuY&m=LiHHncH7191OkF4vZnSdvf7qmC9q13uRiNImGL2Grwk&s=bD9L_fEZ1yLGCO-MpSUcP8icix7bTj0cFrfwyI6_-4k&e= Sent from the Apache Ignite Users mailing list archive at Nabble.com.
