And it will continue hitting us in future. For example, when data compression is implemented, for logical caches compression rate will be poor, as it would be impossbile to build efficient dictionaries in mixed data pages.
On Sat, Sep 30, 2017 at 8:48 AM, Vladimir Ozerov <voze...@gridgain.com> wrote: > Folks, > > Honesly, to me logical caches appears to be a dirty shortcut to mitigate > some inefficient internal implementation. Why can't we merge partition maps > in runtime? This should not be a problem for context-independent affinity > functions (e.g. RendezvousAffinityFunction). From user perspective logic > caches feature is: > 1) Bad API. One cannot define group configuration. All you can do is to > define group name on cache lavel and hope that nobody started another cache > in the same group with different configuration before. > 2) Performance impact for scans, as you have to iterate over mixed data. > > Couldn't we fix partition map problem without cache groups? > > On Sat, Sep 30, 2017 at 2:35 AM, Denis Magda <dma...@apache.org> wrote: > >> Guys, >> >> Another question. Does this capability enabled by default? If yes, how do >> we decide which group a cache goes to? >> >> — >> Denis >> >> > On Sep 29, 2017, at 3:58 PM, Denis Magda <dma...@apache.org> wrote: >> > >> > Igniters, >> > >> > I’ve put on paper the feature from the subj: >> > https://apacheignite.readme.io/docs/logical-caches < >> https://apacheignite.readme.io/docs/logical-caches> >> > >> > Sam, will appreciate if you read through it and confirm I explained the >> topic 100% technically correct. >> > >> > However, are there any negative impacts of having logical caches? This >> page has “Possible Impacts” section unfilled: >> > https://cwiki.apache.org/confluence/display/IGNITE/Logical+Caches < >> https://cwiki.apache.org/confluence/display/IGNITE/Logical+Caches> >> > >> > — >> > Denis >> >> >
