RE: Apache Ignite starts fast and then become really slow with out of memory

Hey Ilya, Yes you are right, the LinkedHashMaps entries are the dominate part. I was concentrating on the reader because I thought there may be an implicit connection.. Those LinkedHashMaps entries are part of the object structure I'm loading to cache, if needed I can send the model code

Apache Ignite starts fast and then become really slow with out of memory

Hey, Guys is this normal…? So many binary readers are opened without reuse? I saw an improvement issue on this https://jira.apache.org/jira/browse/IGNITE-5721 I'm running a simple compute tasks that split around 4K ids to compute job that each one takes from cache bulk of 500

RE: Apache Ignite starts fast and then become really slow with out of memory

Hey, Which thread pools are responsible for the compute jobs and cache operations ? Thanks, Nadav From: Ilya Kasnacheev Sent: Wednesday, February 20, 2019 12:26 PM To: user@ignite.apache.org Subject: Re: Apache Ignite starts fast and then become really slow with out of memory

RE: Apache Ignite starts fast and then become really slow with out of memory

Hey Ilya, I managed to stable the memory and avoid extreme slowness by send compute jobs one by one and not in bulk. The compute jobs takes objects from cache by bulks, so I guess that firing 50 compute jobs on a node where each job takes bulk of 100 is too heavy for it to handle… My node

Compress binary object to save storage spac

Hello, Is there a way in ignite to compress big binary objects ? something like cacheConfiguration.setCompressed(true)? I'm using the latest ignite 2.7 Thanks, Nadav System Architect +972-544821606 DocAuthority.com