ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Page replacement policy improvements (when persistent is enabled)
Date Thu, 16 Aug 2018 09:07:52 GMT
On Thu, Aug 16, 2018 at 2:01 AM, Vladimir Ozerov <vozerov@gridgain.com>

> Hi Dima,
> Putting index pages in separate region is wrong approach, because data
> pages may be equally important on certain workloads, especially in
> heap-organized databases, such as Ignite

Never seen a use case where the data page was more important than the index
page. I think we are getting into a hypothetical land. Most Ignite users
are having the reverse problem - index pages get evicted in the same way as
data pages.

Currently, we are solving it in a most awkward way by trying to give index
pages a different eviction policy. A right solution would be to stick them
into a different region and control the eviction policy for the index
region separately from the data region.


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