This crate contains implementation / helper to create data struct that are memory mapped.
Sometime, you have to deal with vector / data that cannot fit in memory. Moving them to disk and memory map them is a good way to deal with this problem.
That is so simple !
```rust use mmap_vec::MmapVec;
struct Row { id: usize, age: u8, }
let row1 = Row { id: 42, age: 18 }; let row2 = Row { id: 894, age: 99 };
// Create a memory mapped vec 😎 let mut v = MmapVec::new();
// Push can trigger new mmap segment creation, so it can fail. v.push(row1).unwrap(); v.push(row2).unwrap();
// Check the content asserteq!(v[0], row1); asserteq!(&v[..], &[row1, row2]);
// Pop content asserteq!(v.pop(), Some(row2)); asserteq!(v.pop(), Some(row1)); ```
Check the unit tests for more example.
The main idea here is to provide a basic struct Segment
.
This struct provides constant size memory mapped array of type T
.
Wrapping Segment
into a new struct MmapVec
that handle segment growth / shrink does the trick.
Where does the segment are store on disk ?
For now data are stored in /tmp
under a dedicated folder.
UUID V4 are generated in order to avoid collision when creating segment.
bash
❯ ls /tmp/mmap-vec-rs -1
/tmp/mmap-vec-rs/00d977bf-b556-475e-8de5-d35e7baaa39d.seg
/tmp/mmap-vec-rs/6cb81228-9cf3-4918-a3ef-863907b32830.seg
/tmp/mmap-vec-rs/8a86eeaa-1fa8-4535-9e23-6c59e0c9c376.seg
/tmp/mmap-vec-rs/de62bde3-6524-4c4b-b514-24f6a44d6323.seg
Does segment creation is configurable ?
Yes ! Check out test_custom_segment_creator::test_custom_segment_builder
for example.
Since segment creation are manage through a trait. You are free to configure it the way you want.
Does this work on Windows ?
Nope. I am not targeting this OS and would like to keep this crate as simple as possible.
I also would like to reduce dependencies as much as possible.
bash
❯ cargo tree
mmap-vec v0.1.0
├── libc v0.2.147
└── uuid v1.4.1
└── getrandom v0.2.10
├── cfg-if v1.0.0
└── libc v0.2.147
[dev-dependencies]
└── glob v0.3.1
Is this crate production ready ?
Check TODO and DONE bellow for this 😁.
std::alloc::Allocator
to use with std::vec::Vec
License: MIT