rdms
rdms copied to clipboard
Storage library (Work In Progress)
Intelligently handle maximum footprint limit for `m0` level. Once the footprint() reaches 90% of the limit, trigger a auto_commit() and slow down the write ingestion rate.
Goal for Milestone-1 is to provide a minimum viable product for enthusiastic users and early adopters. * [x] Rdms indexes to support [CRUD][CRUD] API. * [x] Rdms instances can be...
We use Empty type across `rdms` type mechanics to fill implementation gaps. Although it works well, we would like to consider using the `!` (never_type) instead of Empty. One immediate...
Using trait object gives convenience of abstraction. But performance can be an issue. Once such design choice is core::IndexIter trait object. Validate the performance penalty in using IndexIter and if...
Given that footprint calculation need to be managed across set/set_cas/delete and its entry variant along with managing previous delta versions, it gets quite complicated. Review the present implementation for correctness...
Right now `mmap` is implemented for index-file. `robt` can be configured to use a separate value-log-file and `mmap` feature is not implemented for value-log file. We should experiment an implementation...
This issue is applicable only when ``rdms`` indexes are configured to manage older versions for each entries. Following are the read APIs defined by the ``Reader`` trait. * get() *...
Rdms, when configured with version control, won't destory older values for index entries. In other words, from the first mutation that **CREATE** a {key,value} entry in the index, to all...
When replication has to be supported for Rdms indexes, a separate sequence-number tree need to be implemented as part of the every level.
Rdms indexes can support full table scan, by providing an iterator handle to iterate over every single entry in sort order. Since by design rdms also provide concurrent write operation,...