ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: How does Ignite garbage collect unused pages?
Date Tue, 12 Jun 2018 23:32:24 GMT
Whenever you add or remove an entry, it changes the size of a page which
can lead to page movement between free list. According to this page, the
page defragmentation/compaction happens in the background and when a
threshold is met: https://apacheignite.readme.io/docs/memory-defragmentation

Hope Ignite persistence experts can shine more light on this.

--
Denis

On Tue, Jun 12, 2018 at 3:12 PM John Wilson <sami.hailu.15@gmail.com> wrote:

> thanks. But *when* does that happen - i.e. when is the decision made to
> move pages? Is this part of the cache.put path or a separate thread?
>
> On Tue, Jun 12, 2018 at 1:03 PM, Denis Magda <dmagda@apache.org> wrote:
>
> > A page is moved between free lists that used to track pages of similar
> free
> > space left:
> >
> https://apacheignite.readme.io/docs/memory-architecture#section-free-lists
> >
> > --
> > Denis
> >
> >
> > On Tue, Jun 12, 2018 at 12:35 PM John Wilson <sami.hailu.15@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > How does Ignite free unused pages? Is there some kind of background
> > thread
> > > process that scans unused pages?
> > >
> > > Thanks,
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message