To my knowledge, in Ignite 2.0 we will have Memory Policies, and multiple caches will be able to reuse the same policy. Since the memory size will be defined at the policy level, it will essentially solve this problem.
Am I wrong? D. On Thu, Sep 15, 2016 at 12:15 PM, Igor Rudyak <irud...@gmail.com> wrote: > +1 > > On Thu, Sep 15, 2016 at 12:11 PM, Denis Magda <dma...@gridgain.com> wrote: > > > +1 > > > > I’ve faced with such injuries as well and this feature sounds reasonable > > for me. > > > > However, is this going to be supported in the new memory architecture the > > community has been working on? Alex G., can you comment? > > > > — > > Denis > > > > > On Sep 15, 2016, at 12:07 PM, Valentin Kulichenko < > > valentin.kuliche...@gmail.com> wrote: > > > > > > Folks, > > > > > > I'm seeing more and more requests from users to add an option to > specify > > > the off-heap memory limit globally, for all the caches in total. > > Currently > > > we allow this only on per-cache level, which can be not very usable > > > sometimes. > > > > > > E.g., imagine that you have 100GB of RAM and two caches with 50GB limit > > for > > > each of them. At some point one of the caches can consume all 50GB, > while > > > the second is almost empty. You can't add anything to the first cache > > > regardless of the fact that you still have lots of memory available. > > > > > > Can we add such parameter? > > > > > > -Val > > > > >
