Crates.io | dcl_data_structures |
lib.rs | dcl_data_structures |
version | 0.7.0 |
source | src |
created_at | 2023-07-06 09:18:32.456031 |
updated_at | 2024-11-26 05:57:31.509089 |
description | Data structures for for deep_causality crate. |
homepage | |
repository | https://github.com/deepcausality/deep_causality.rs |
max_upload_size | |
id | 909704 |
size | 414,072 |
High performance SlidingWindow datastructures used in DeepCausality and elsewhere.
RingBuffer is a high-performance, lock-free data structure implementation inspired by the LMAX Disruptor pattern. The RingBuffer supports the following configurations:
ArrayGrid is an abstraction over scalars, vectors, and low dimensional matrices similar to a tensor. In contrast to a tensor, an ArrayGrid is limited to low dimensions (1 to 4), only allowing a scalar, vector, or matrix type. Still, all of them are represented as a static fixed-size const generic array. Fixed-sized arrays allow for several compiler optimizations, including a cache-aligned data layout and the removal of runtime array boundary checks because all structural parameters are known upfront, providing a significant performance boost over tensors.
The sliding window implementation over-allocates to trade space (memory) for time complexity by delaying the rewind operation when hitting the end of the underlying data structure. Specifically, a sliding window of size N can hold, without any array copy, approximately C-1 elements, where C is the total capacity defined as NxM with N as the window size and M as a multiple. This crate has two implementations, one over vector and the second over a const generic array. The const generic implementation is significantly faster than the vector-based version.
unsafe
feature flag.Set value:
Dimension | Safe Implementation | Unsafe Implementation | Improvement |
---|---|---|---|
1D Grid | 604.71 ps | 271.38 ps | 55.1% |
2D Grid | 581.33 ps | 417.39 ps | 28.2% |
3D Grid | 862.16 ps | 577.04 ps | 33.0% |
4D Grid | 1.137 ns | 812.62 ps | 28.5% |
More details on performance can be found in the Performance section of the ArrayGrid document.
Batch Size | Throughput | Latency |
---|---|---|
1 | 220.47 Melem/s | 4.54 ms |
10 | 1.65 Gelem/s | 604.88 ยตs |
50 | 1.67 Gelem/s | 597.67 ยตs |
100 | 1.68 Gelem/s | 596.12 ยตs |
More details on performance can be found in the Performance section of the RingBuffer document.
Single Push:
Implementation | Single Push Time | Notes |
---|---|---|
ArrayStorage | ~2.08ns | Optimized for continuous access patterns |
VectorStorage | ~2.5ns | Good for dynamic sizing |
UnsafeVectorStorage | ~2.3ns | Better performance than safe vector |
UnsafeArrayStorage | ~1.9ns | Best performance for sequential and batch operations |
Sequential Operations:
Implementation | Operation Time | Notes |
---|---|---|
UnsafeArrayStorage | ~550ps | Best cache utilization |
ArrayStorage | ~605ps | Excellent cache locality |
UnsafeVectorStorage | ~750ps | Good for mixed workloads |
VectorStorage | ~850ps | Most predictable |
More details on performance can be found in the Performance section of the SlidingWindow document.
Just run:
cargo add dcl_data_structures
ArrayGrid:
SlidingWindow:
The project took inspiration from:
Contributions are welcomed especially related to documentation, example code, and fixes. If unsure where to start, just open an issue and ask.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in deep_causality by you, shall be licensed under the MIT licence, without any additional terms or conditions.
This project is licensed under the MIT license.
For details about security, please read the security policy.