You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Dmitriy Setrakyan <ds...@apache.org> on 2017/09/04 03:11:38 UTC

Fwd: Limiting the size of Persistent Store and clearing data on restart

Cross sending to dev@.

Does anyone know why we still have swapEnabled property in master?

D.

---------- Forwarded message ----------
From: Denis Mekhanikov <dm...@gmail.com>
Date: Fri, Sep 1, 2017 at 9:51 AM
Subject: Re: Limiting the size of Persistent Store and clearing data on
restart
To: user@ignite.apache.org


Sorry, I didn't know that. I found a bunch of matches by "swapEnabled"
keyword on master branch in the project, mostly in benchmarks
configurations. These properties should probably be removed not to confuse
readers.

пт, 1 сент. 2017 г. в 19:23, Dmitriy Setrakyan <ds...@apache.org>:

> On Fri, Sep 1, 2017 at 1:41 PM, Denis Mekhanikov <dm...@gmail.com>
> wrote:
>
>> Regarding your second question: looks like you don't actually need
>> persistence. Its purpose is the opposite: to save cache data between
>> restarts.
>> If you use persistence to store more data than RAM available, then you
>> can enable swap space: https://apacheignite.readme.io/v1.9/docs/off-heap-
>> memory#section-swap-space
>>
>
> Denis, starting with 2.1, Ignite does not have the swap space anymore,
> since it never worked well and kept hurting the performance. We recommend
> now that users do use persistence whenever the data size is bigger than the
> available memory size.
>