Re: memory-only mode for Ignite indexes

Hi Igniters, I may repeat what was said early, but still: I prefer way of speeding up indexes proposed by Vladimir in addition to page replacement optimizations related to index pages. Also recently Ivan Rakov created issue intended to optimize findPageForReplacement method, it can also help

Re: memory-only mode for Ignite indexes

Dima, Denis, Please stp wanting this! :-) Guys, there are no in-memory indexes just to be in-memory. Let me briefly explain what other vendors do and why. There are three approaches: 1) You may create *skip-list* based in-memory index. Goal - speedup *READS*, not writes. Examples: MS

Re: memory-only mode for Ignite indexes

Truly like the idea of having a separate "indexes in memory only mode" regardless of the optimizations Vladimir keeps track of. In my observations, some database vendors support this as the only mode requiring to rebuild the indexes on a restart which confirms that there is a demand for this

Re: memory-only mode for Ignite indexes

Agree. On Mon, May 7, 2018 at 5:20 PM, Dmitriy Setrakyan wrote: > On Mon, May 7, 2018 at 2:09 AM, Vladimir Ozerov > wrote: > > > Hi Dima, > > > > Update with indexes would definitely be slower than update without them. > > The question is how much

Re: memory-only mode for Ignite indexes

On Mon, May 7, 2018 at 2:09 AM, Vladimir Ozerov wrote: > Hi Dima, > > Update with indexes would definitely be slower than update without them. > The question is how much slower. For now the slowdown comes mostly from > excessive data page reads ([1] and [2] in my previous

Re: memory-only mode for Ignite indexes

Hi Dima, Update with indexes would definitely be slower than update without them. The question is how much slower. For now the slowdown comes mostly from excessive data page reads ([1] and [2] in my previous email) leading to page evictions and additional IO. To the contrast, usually only a

Re: memory-only mode for Ignite indexes

Vladimir, my comments are inline... On Sat, May 5, 2018 at 6:12 AM, Vladimir Ozerov wrote: > In general I do not support this initiative. There are two serious reasons > for that: > 1) Our indexes are slow on updates due to architectural flaws. First, every > index entry

Re: memory-only mode for Ignite indexes

In general I do not support this initiative. There are two serious reasons for that: 1) Our indexes are slow on updates due to architectural flaws. First, every index entry must be of fixed size. For this reason we cannot inline full values in general case and suffer from data page lookups [1].