Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CADM=oMY2dq-fbWE0xQxb0g6hcKmJuDc_POH7cOPiDG-CD8ajeA@mail.gmail.com>
References: <CADM=oMafNO8vL_YqCs7hT=XV5+PLZXGB5hiXjiOxriAB=j-8uw@mail.gmail.com>
 <CA+0=VoU7r-MMYRdjsPP3A4kN24rAdX4vJTE=ZVHFihdzneP_eQ@mail.gmail.com> <CADM=oMY2dq-fbWE0xQxb0g6hcKmJuDc_POH7cOPiDG-CD8ajeA@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Wed, 5 Apr 2017 03:55:03 -0700
Message-ID: <CA+0=VoVna25yN+tpVNFpEmc0r=Os=mp6QnDb4Q5m3mQ+gW33Rw@mail.gmail.com>
Subject: Re: IGNITE-4535 : Add option to store deserialized values on-heap
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a11479434eeb9a9054c693bec
archived-at: Wed, 05 Apr 2017 10:55:47 -0000

--001a11479434eeb9a9054c693bec
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 5, 2017 at 2:52 AM, Ilya Lantukh <ilantukh@gridgain.com> wrote:

> Dmitry,
>
> 1. Setting an eviction policy should not be a mechanism to enable the
> > on-heap cache. We already have eviction policies off-heap as well, and
> they
> > don't enable anything. On top of that, the eviction policy should not be
> a
> > requirement for the on-heap cache. User should still be able to enable
> the
> > on-heap cache, even if it grows indefinitely without evictions. We should
> > have a more intuitive flag here.
>
>
> It doesn't make any sence to me to enable on-heap cache without evictions:
> it will result in having all data both in on-heap and off-heap memory. If
> we want to support such use case, we should implement a separate on-heap
> only mode with page memory disabled.
>

I agree that this would cause a double memory consumption, but yet again,
we don't have a pure on-heap cache yet. Until we do, we should not require
an eviction policy present for the on-heap caches.

--001a11479434eeb9a9054c693bec--