(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
p;
!isBinaryEnabled(ccfg));
ctx.resource().injectGeneric(res.defaultAffMapper());
return res;
}
Thanks,
Raymond.
*From:* Raymond Wilson [mailto:raymond_wil...@trimble.com]
*Sent:* Monday, February 13, 2017 2:43 PM
*To:* user@ignite.apache.org
*Subject:* RE: Effective si
Ah, I found the CopyOnRead flag in the cache configuration.
Unfortunately, it seems to have the same behaviour regardless of the
setting for this flag.
If I create an example like the below, it seems that querying the same
element from the cache many times takes about the same amount of time
