Re: Setting Cache Size using Max Records

>From what i have read so far, seems like if i have 2 caches each to be configured with 50MB, then i need to define 2 identical regions with unique names and apply to each of the caches. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Setting Cache Size using Max Records

Thanks Denis this helps. Btw, one thing to check, if you create a 25MB region and multiple cache's are associated to that region, do all the caches share the region capacity or just share the configuration but each cache will be allocated a 25MB capacity? -- Sent from:

Re: Setting Cache Size using Max Records

1. There is no any public API for that but you can follow a workaround suggested here . If you have a POJO class of your domain object, then create an instance, convert it to BinaryObjectImpl and get the array size (as

Re: Setting Cache Size using Max Records

Yes, user upfront defines a config and the idea indeed is to convert the number of records to total bytes. Followup around this. Given i want to calculate the exact row entry size upfront, even before the data is added. Couple of queries, 1. Is there a way(api) just based on the Cache (table),

Re: Setting Cache Size using Max Records

Victor, Is it correct to assume that the users define this configuration first and only then you span up an Ignite cluster for them? If it's so, then you can translate a user-defined number of records to final data region size. The formula might be as follows - "data_region_size =

Re: Setting Cache Size using Max Records

Iiya/ Denis, I am aware of the Data Region with max size as bytes. I was looking for way to do this via number of records. Anyway, seems there is no way in Ignite to do this today. I am looking at couple of other options to achieve this, for that same i am looking at a way to calculate the

Re: Setting Cache Size using Max Records

Hello! You can have a data region configured for this specific cache, with max size (in bytes) and page eviction on. Regards, -- Ilya Kasnacheev чт, 25 июн. 2020 г. в 07:16, Victor : > Hi Denis, > > For our product we are using an in-house solution where we expose the size > in records. Now

Re: Setting Cache Size using Max Records

Hi Denis, For our product we are using an in-house solution where we expose the size in records. Now we are looking at replacing it with Ignite. So we wanted to make the experience seamless and let the end user's continue to set the same configuration they are familiar with, rather than adding a

Re: Setting Cache Size using Max Records

Hi Vic, That’s unsupported for the off-heap memory. You can only limit memory usage based on the size in bytes. Please share more details of why this type of records eviction is needed. We might suggest an alternate solution. Denis On Wednesday, June 24, 2020, Victor wrote: > Hi, > > I am

Setting Cache Size using Max Records

Hi, I am looking to set the cache size for off-heap via number of max records instead of max bytes. Similar to how LRU eviction policy for on-heap can set it. Haven't found anything around that. Is that doable, if yes, how do i go about it? Thanks, Vic -- Sent from: