(at least for those workflows) is much longer than
that.
Thanks,
Raymond.
*From:* Pavel Tupitsyn [mailto:ptupit...@apache.org]
*Sent:* Tuesday, February 14, 2017 2:16 AM
*To:* user@ignite.apache.org
*Subject:* Re: Effective size limit for cache items in Ignite
Hi Raymond,
CopyOnRead setting
t;
> storeVal,
>
> ctx.config().isPeerClassLoadingEnabled() &&
> !isBinaryEnabled(ccfg));
>
>
>
> ctx.resource().injectGeneric(res.defaultAffMapper());
>
>
>
> return res;
>
> }
>
>
>
> Thanks,
>
> Raym
gt;]
*Sent:* Monday, February 13, 2017 11:35 AM
*To:* user@ignite.apache.org
*Subject:* Effective size limit for cache items in Ignite
Hi,
What is the practical size limit for items in an Ignite cache?
I suspect the answer is something “As large as the memory you have to hold
it”, but my que
he cache items
for (int i = 0; i < 3; i++)
{
MyCacheClass first = cache.Get("First");
}
}
*From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
*Sent:* Monday, February 13, 2017 11:35 AM
*To:* user@ignite.apa
Hi,
What is the practical size limit for items in an Ignite cache?
I suspect the answer is something “As large as the memory you have to hold
it”, but my question is more aimed at the practicality of large items in a
cache due to the overhead of pulling copies of the items out of the cache
