Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DF408200B85 for ; Thu, 15 Sep 2016 21:44:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DDC49160AC6; Thu, 15 Sep 2016 19:44:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2E385160ABA for ; Thu, 15 Sep 2016 21:44:10 +0200 (CEST) Received: (qmail 8877 invoked by uid 500); 15 Sep 2016 19:44:09 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 8860 invoked by uid 99); 15 Sep 2016 19:44:09 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Sep 2016 19:44:09 +0000 Received: from mail-yw0-f180.google.com (mail-yw0-f180.google.com [209.85.161.180]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id E74931A0046 for ; Thu, 15 Sep 2016 19:44:08 +0000 (UTC) Received: by mail-yw0-f180.google.com with SMTP id g192so72080216ywh.1 for ; Thu, 15 Sep 2016 12:44:08 -0700 (PDT) X-Gm-Message-State: AE9vXwPP8wrumbbZb6g2HNQgQgPpsY8z7moRpPHSGava9PXQhq4YNMvrujsC7K6yaDgrRmQFWw2BNFJ8HnNAkOvA X-Received: by 10.13.198.194 with SMTP id i185mr10084464ywd.132.1473968648066; Thu, 15 Sep 2016 12:44:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.178.205 with HTTP; Thu, 15 Sep 2016 12:43:27 -0700 (PDT) In-Reply-To: References: <22374872-5873-4011-BB15-E96988F4B074@gridgain.com> From: Dmitriy Setrakyan Date: Thu, 15 Sep 2016 12:43:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Global off-heap memory limit To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary=001a114e6082ade6a3053c9111b9 archived-at: Thu, 15 Sep 2016 19:44:11 -0000 --001a114e6082ade6a3053c9111b9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wrote: > +1 > > On Thu, Sep 15, 2016 at 12:11 PM, Denis Magda wrote= : > > > +1 > > > > I=E2=80=99ve faced with such injuries as well and this feature sounds r= easonable > > for me. > > > > However, is this going to be supported in the new memory architecture t= he > > community has been working on? Alex G., can you comment? > > > > =E2=80=94 > > Denis > > > > > On Sep 15, 2016, at 12:07 PM, Valentin Kulichenko < > > valentin.kulichenko@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 lim= it > > 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 > > > > > --001a114e6082ade6a3053c9111b9--