rust-sieve-cache

KO | EN

gitlite — search

#hacktoberfest #react #llm #golang #android #rust #deep-learning #docker #windows #awesome #cli #pytorch #security #open-source

rust-sieve-cache

(★ 30)

SIEVE cache replacement policy for Rust.

rust-sieve-cache Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

[![dependency status](https://deps.rs/repo/github/jedisct1/rust-sieve-cache/status.svg)](https://deps.rs/repo/github/jedisct1/rust-sieve-cache)

# SIEVE cache

A high-performance implementation of the [SIEVE](http://sievecache.com) cache replacement algorithm for Rust, with single-threaded, thread-safe, and memory-bounded variants.

- [API documentation](https://docs.rs/sieve-cache)
- [`crates.io` page](https://crates.io/crates/sieve-cache)

## Overview

SIEVE is an eviction algorithm that is simpler than LRU but achieves state-of-the-art efficiency on skewed workloads. It works by maintaining a single bit per entry that tracks whether an item has been "visited" since it was last considered for eviction.

### Key Features

- **Simple and efficient**: SIEVE requires less state than LRU or LFU algorithms
- **Good performance on skewed workloads**: Particularly effective for real-world access patterns
- **Adaptive capacity management**: Recommendation system to optimize cache size based on utilization
- **Memory-bounded caching**: Optional weight-based eviction via the `Weigh` trait
- **Multiple implementations**:
  - `SieveCache`: Core single-threaded implementation
  - `SyncSieveCache`: Thread-safe wrapper using a single lock
  - `ShardedSieveCache`: High-concurrency implementation using multiple locks
  - `WeightedSieveCache`: Memory-bounded wrapper that evicts by weight
  - `WeightedSyncSieveCache`: Thread-safe memory-bounded cache
  - `WeightedShardedSieveCache`: Sharded memory-bounded cache

This implementation exposes the same API as the `clock-pro` and `arc-cache` crates, so it can be used as a drop-in replacement for them in existing applications.

## Basic Usage

The library provides cache implementations with different threading and eviction characteristics.

### `SieveCache` - Single-Threaded Implementation

The core `SieveCache` implementation is designed for single-threaded use. It's the most efficient option when thread safety isn't required.

```rust
use sieve_cache::SieveCache;

// Create a new cache with a specific capacity
let mut cache: SieveCache<String, String> = SieveCache::new(100000).unwrap();

// Insert key/value pairs into the cache
cache.insert("foo".to_string(), "foocontent".to_string());
cache.insert("bar".to_string(), "barcontent".to_string());

// Retrieve a value from the cache (returns a reference to the value)
assert_eq!(cache.get("foo"), Some(&"foocontent".to_string()));

// Check if a key exists in the cache
assert!(cache.contains_key("foo"));
assert!(!cache.contains_key("missing_key"));

// Get a mutable reference to a value
if let Some(value) = cache.get_mut("foo") {
   *value = "updated_content".to_string();
}

// Remove an entry from the cache
let removed_value = cache.remove("bar");
assert_eq!(removed_value, Some("barcontent".to_string()));

// Query cache information
assert_eq!(cache.len(), 1);       // Number of entries
assert_eq!(cache.capacity(), 100000);  // Maximum capacity
assert!(!cache.is_empty());       // Check if empty

// Manual eviction (normally handled automatically when capacity is reached)
let evicted = cache.evict();  // Returns and removes a value that wasn't recently accessed

// Get a recommendation for optimal cache capacity based on current utilization
let recommended = cache.recommended_capacity(0.5, 2.0, 0.3, 0.7);
println!("Recommended capacity: {}", recommended);
```

## Thread-Safe Implementations

These implementations are available when using the appropriate feature flags:
- `SyncSieveCache` is available with the `sync` feature (enabled by default)
- `ShardedSieveCache` is available with the `sharded` feature (enabled by default)

### `SyncSieveCache` - Basic Thread-Safe Cache

For concurrent access from multiple threads, you can use the `SyncSieveCache` wrapper, which provides thread safety with a single global lock:

```rust
use sieve_cache::SyncSieveCache;
use std::thread;

// Create a thread-safe cache
let cache = SyncSieveCache::new(100000).unwrap();

// The cache can be safely cloned and shared between threads
let cache_clone = cache.clone();

// Insert from the main thread
cache.insert("foo".to_string(), "foocontent".to_string());

// Access from another thread
let handle = thread::spawn(move || {
    // Insert a new key
    cache_clone.insert("bar".to_string(), "barcontent".to_string());

// Get returns a clone of the value, not a reference (unlike non-thread-safe version)
    assert_eq!(cache_clone.get(&"foo".to_string()), Some("foocontent".to_string()));
});

// Wait for the thread to complete
handle.join().unwrap();

// Check if keys exist
assert!(cache.contains_key(&"foo".to_string()));
assert!(cache.contains_key(&"bar".to_string()));

// Remove an entry
let removed = cache.remove(&"bar".to_string());
assert_eq!(removed, Some("barcontent".to_string()));

// Perform multiple operations atomically with exclusive access
cache.with_lock(|inner_cache| {
    // Operations inside this closure have exclusive access to the cache
    inner_cache.insert("atomic1".to_string(), "value1".to_string());
    inner_cache.insert("atomic2".to_string(), "value2".to_string());

// We can check internal state as part of the transaction
    assert_eq!(inner_cache.len(), 3);
});
```

Key differences from the non-thread-safe version:
- Methods take `&self` instead of `&mut self`
- `get()` returns a clone of the value instead of a reference
- `with_lock()` method provides atomic multi-operation transactions

### `ShardedSieveCache` - High-Performance Thread-Safe Cache

For applications with high concurrency requirements, the `ShardedSieveCache` implementation uses multiple internal locks (sharding) to reduce contention and improve throughput:

```rust
use sieve_cache::ShardedSieveCache;
use std::thread;
use std::sync::Arc;

// Create a sharded cache with default shard count (16)
// We use Arc for sharing between threads
let cache = Arc::new(ShardedSieveCache::new(100000).unwrap());

// Alternatively, specify a custom number of shards
// let cache = Arc::new(ShardedSieveCache::with_shards(100000, 32).unwrap());

// Insert data from the main thread
cache.insert("foo".to_string(), "foocontent".to_string());

// Use multiple worker threads to insert data concurrently
let mut handles = vec![];
for i in 0..8 {
    let cache_clone = Arc::clone(&cache);
    let handle = thread::spawn(move || {
        // Each thread inserts multiple values
        for j in 0..100 {
            let key = format!("key_thread{}_item{}", i, j);
            let value = format!("value_{}", j);
            cache_clone.insert(key, value);
        }
    });
    handles.push(handle);
}

// Wait for all threads to complete
for handle in handles {
    handle.join().unwrap();
}

// Shard-specific atomic operations
// with_key_lock locks only the shard containing the key
cache.with_key_lock(&"foo", |shard| {
    // Operations inside this closure have exclusive access to the specific shard
    shard.insert("related_key1".to_string(), "value1".to_string());
    shard.insert("related_key2".to_string(), "value2".to_string());

// We can check internal state within the transaction
    assert!(shard.contains_key(&"related_key1".to_string()));
});

// Get the number of entries across all shards
// Note: This acquires all shard locks sequentially
let total_entries = cache.len();
assert_eq!(total_entries, 803); // 800 from threads + 1 "foo" + 2 related keys

// Access shard information
println!("Cache has {} shards with total capacity {}",
         cache.num_shards(), cache.capacity());
```

#### How Sharding Works

The `ShardedSieveCache` divides the cache into multiple independent segments (shards), each protected by its own mutex. When an operation is performed on a key:

1. The key is hashed to determine which shard it belongs to
2. Only that shard's lock is acquired for the operation
3. Operations on keys in different shards can proceed in parallel

This design significantly reduces lock contention when operations are distributed across different keys, making it ideal for high-concurrency workloads.

## Memory-Bounded Caches

The `weighted` feature (enabled by default) adds cache implementations that evict based on a memory budget rather than just entry count. Each key and value type implements the `Weigh` trait, which reports its approximate memory footprint. Blanket implementations are provided for common types (`String`, `Vec<T>`, `Box<T>`, primitives, etc.).

### `WeightedSieveCache` - Single-Threaded

```rust
use sieve_cache::{Weigh, WeightedSieveCache};

// Create a cache that holds at most 10 entries and 1 KB of weight
let mut cache = WeightedSieveCache::new(10, 1024).unwrap();

cache.insert("key".to_string(), "value".to_string());
assert!(cache.current_weight() > 0);
assert!(cache.current_weight() <= cache.max_weight());

// Weight is snapshotted at insert time.
// Mutating via get_mut does not change the tracked weight.
if let Some(v) = cache.get_mut("key") {
    *v = "a much longer string".to_string();
}
// current_weight still reflects the original "value"

// Entries are evicted automatically when inserting would exceed max_weight.
// A single oversized entry is allowed as the sole occupant.
```

Thread-safe variants follow the same pattern as their non-weighted counterparts:

- `WeightedSyncSieveCache::new(capacity, max_weight)` -- single-lock thread safety
- `WeightedShardedSieveCache::new(capacity, max_weight)` -- sharded, with the weight budget distributed across shards

## Feature Flags

This crate provides the following feature flags to control which implementations are available:

- `sync`: Enables `SyncSieveCache` and `WeightedSyncSieveCache` (enabled by default)
- `sharded`: Enables `ShardedSieveCache` and `WeightedShardedSieveCache` (enabled by default)
- `weighted`: Enables `WeightedSieveCache`, `Weigh` trait, and the weighted sync/sharded variants (enabled by default)

If you only need specific implementations, you can select just the features you need:

```toml
# Only use the core implementation
sieve-cache = { version = "1", default-features = false }

# Core + sync, no weighted
sieve-cache = { version = "1", default-features = false, features = ["sync"] }

# Everything except sharding
sieve-cache = { version = "1", default-features = false, features = ["sync", "weighted"] }

# For documentation tests to work correctly
sieve-cache = { version = "1", features = ["doctest"] }
```

## Adaptive Cache Sizing

The library includes a mechanism to recommend optimal cache sizes based on current utilization patterns.

### How it Works

The `recommended_capacity` function analyzes:
- The ratio of "visited" entries (recently accessed) to total entries
- How full the cache is relative to its capacity
- User-defined thresholds for scaling decisions

Based on this analysis, it recommends:
- Increasing capacity when many entries are frequently accessed (high utilization)
- Decreasing capacity when few entries are frequently accessed (low utilization)
- Maintaining current capacity when utilization is within normal parameters

### Usage

```rust
use sieve_cache::SieveCache;

let mut cache = SieveCache::<String, String>::new(1000).unwrap();

// Add and access items...
// (usage pattern will affect the recommendation)

// Get recommended capacity with custom parameters
let recommended = cache.recommended_capacity(
    0.5,    // min_factor: Never go below 50% of current capacity
    2.0,    // max_factor: Never exceed 200% of current capacity
    0.3,    // low_threshold: Consider decreasing below 30% utilization
    0.7     // high_threshold: Consider increasing above 70% utilization
);

println!("Current capacity: {}", cache.capacity());
println!("Recommended capacity: {}", recommended);

// Optionally resize your cache based on the recommendation
// (requires creating a new cache with the recommended size)
if recommended != cache.capacity() {
    let mut new_cache = SieveCache::new(recommended).unwrap();

// Transfer entries from old cache to new cache
    for (key, value) in cache.iter() {
        new_cache.insert(key.clone(), value.clone());
    }

// Use the new cache from now on
    cache = new_cache;
}
```

This adaptive sizing capability is available in all three cache implementations:

```
// Thread-safe version (with "sync" feature enabled)
// use sieve_cache::SyncSieveCache;
// let cache = SyncSieveCache::<String, u32>::new(1000).unwrap();
// let recommended = cache.recommended_capacity(0.5, 2.0, 0.3, 0.7);

// Sharded high-concurrency version (with "sharded" feature enabled)
// use sieve_cache::ShardedSieveCache;
// let cache = ShardedSieveCache::<String, u32>::new(1000).unwrap();
// let recommended = cache.recommended_capacity(0.5, 2.0, 0.3, 0.7);
```

## Performance Considerations

Choosing the right cache implementation depends on your workload:

- **Single-threaded usage**: Use `SieveCache` - it's the most efficient with the lowest overhead
- **Moderate concurrency**: Use `SyncSieveCache` - simple and effective with moderate thread count
- **High concurrency**: Use `ShardedSieveCache` - best performance with many threads accessing different keys
  - Sharding is most effective when operations are distributed across many keys
  - If most operations target the same few keys (which map to the same shards), the benefits may be limited
  - Generally, 16-32 shards provide a good balance of concurrency and overhead for most applications

rust-sieve-cache

rust-sieve-cache Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

rust-sieve-cache

rust-sieve-cache Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README