Struct marble::Marble

pub struct Marble { /* private fields */ }

Garbage-collecting object store. A nice solution to back a pagecache, for people building their own databases.

ROWEX-style concurrency: readers rarely block on other readers or writers, but serializes writes to be friendlier for SSD GC. This means that writes should generally be performed by some background process whose job it is to clean logs etc…

Implementations

impl Marble

pub fn open<P: AsRef<Path>>(path: P) -> Result<Marble>

pub fn open_with_config(config: Config) -> Result<Marble>

pub fn read(&self, pid: ObjectId) -> Result<Option<Vec<u8>>>

Read a object out of storage. If this object is unknown or has been removed, returns Ok(None).

May be called concurrently with background calls to maintenance and write_batch.

pub fn file_statistics(&self) -> FileStats

Statistics about current files.

pub fn write_batch(
    &self,
    write_batch: HashMap<ObjectId, Option<Vec<u8>>>
) -> Result<()>

Write a batch of objects to disk. This function is crash-atomic but NOT runtime atomic. If you are concurrently serving reads, and require atomic batch semantics, you should serve reads out of an in-memory cache until this function returns. Creates at least one file per call. Performs several fsync calls per call. Ideally, you will heavily batch objects being written using a logger of some sort before calling this function occasionally in the background, then deleting corresponding logs after this function returns.

pub fn maintenance(&self) -> Result<usize>

Defragments backing storage files, blocking concurrent calls to write_batch but not blocking concurrent calls to read. Returns the number of rewritten objects.