Dima, By "out of question" I meant that 3rd party persistence should work out of the box when IEP-22 is ready. No changes should be required there.
As far as persistence vs memory, most probably yes, there might be some differences. Specifically, when data load starts and persistence is enabled, we will bypass free lists and write data to new blocks. This way, overall data will need more pages than when loaded in normal mode. This is a kind of trade-off you face when loading speed is important (at the very least Oracle works this way, most probably other vendors does the same). But this approach may be not applicable for in-memory mode, where total number of pages is limited, and we do not want to hit page eviction. To summarize - some optimizations which are applicable for persistent mode will not be applicable for in-memory. Vladimir. On Thu, Aug 16, 2018 at 11:41 AM Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Thu, Aug 16, 2018 at 1:24 AM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > Hi Denis, > > > > This IEP is mostly about how we work with our own indexes and pages. So > 3rd > > party DB is out of question. > > > > Why? I think 3rd party DB will be supported automatically with CacheStore. > However, do we need to do something different for memory-only vs. > memory+disk? > > D. >
