Re: Page replacement policy improvements (when persistent is enabled)

2018-08-16 Thread Dmitriy Pavlov
Hi Igniters, I feel monitoring will provide us with the necessary knowledge about how to change. I have no idea how region separation can help with performance. But it could be an additional challenge for users to correctly configure separate regions. Sincerely, Dmitriy Pavlov чт, 16 авг. 2018

Re: Page replacement policy improvements (when persistent is enabled)

2018-08-16 Thread Dmitriy Setrakyan
On Thu, Aug 16, 2018 at 2:27 AM, Vladimir Ozerov wrote: > Dima, > > None database I know use separate regions for index pages due to the reason > I expressed above. Instead, they split all pages into two groups - hot and > cold. With certain rules on how to move pages inside and between these >

Re: Page replacement policy improvements (when persistent is enabled)

2018-08-16 Thread Vladimir Ozerov
Dima, None database I know use separate regions for index pages due to the reason I expressed above. Instead, they split all pages into two groups - hot and cold. With certain rules on how to move pages inside and between these groups. None of these algorithms are complex enough. In fact, they

Re: Page replacement policy improvements (when persistent is enabled)

2018-08-16 Thread Dmitriy Setrakyan
On Thu, Aug 16, 2018 at 2:01 AM, Vladimir Ozerov wrote: > 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

Re: Page replacement policy improvements (when persistent is enabled)

2018-08-16 Thread Vladimir Ozerov
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. At the moment we'd better focus on monitoring.to better understand usages patterns. This would give us solid

Re: Page replacement policy improvements (when persistent is enabled)

2018-08-03 Thread Dmitriy Setrakyan
Vladimir, Are we only counting timestamp of the last access? In that case, it would create a problem. We should also count number of times a page has been touched within a certain time frame, e.g. last hour or so. In this case, index pages would not be evicted as they get touched the most. I

Re: Page replacement policy improvements (when persistent is enabled)

2018-08-03 Thread Dmitriy Pavlov
Hi Vladimir, I really feel that page replacement approach can be improved. Currently I don't think that page nature will give us much, because usage frequency can be independent to page type. I also noticed a couple of tickets were done by Ilya Kasnacheev and Eugeniy Stanilovskly, which were