| Crates.io | fastbloom |
| lib.rs | fastbloom |
| version | 0.14.0 |
| created_at | 2024-02-23 04:21:37.915042+00 |
| updated_at | 2025-07-30 06:51:07.422555+00 |
| description | The fastest Bloom filter in Rust. No accuracy compromises. Full concurrency support and compatible with any hasher. |
| homepage | https://github.com/tomtomwombat/fastbloom/ |
| repository | https://github.com/tomtomwombat/fastbloom/ |
| max_upload_size | |
| id | 1150087 |
| size | 96,644 |
The fastest Bloom filter in Rust. No accuracy compromises. Full concurrency support and compatible with any hasher.
fastbloom is a fast, flexible, and accurate Bloom filter implemented in Rust. fastbloom's default hasher is SipHash-1-3 using randomized keys but can be seeded or configured to use any hasher. fastbloom is 2-400 times faster and magnitudes more accurate than existing Bloom filter implementations. fastbloom's AtomicBloomFilter is a concurrent Bloom filter that avoids lock contention.
Due to a different (improved!) algorithm in 0.14.x, Bloomfilters have incompatible serialization/deserialization with prior versions.
# Cargo.toml
[dependencies]
fastbloom = "0.14.0"
Basic usage:
use fastbloom::BloomFilter;
let mut filter = BloomFilter::with_num_bits(1024).expected_items(2);
filter.insert("42");
filter.insert("🦀");
Instantiate with a target false positive rate:
use fastbloom::BloomFilter;
let filter = BloomFilter::with_false_pos(0.001).items(["42", "🦀"]);
assert!(filter.contains("42"));
assert!(filter.contains("🦀"));
Use any hasher:
use fastbloom::BloomFilter;
use ahash::RandomState;
let filter = BloomFilter::with_num_bits(1024)
.hasher(RandomState::default())
.items(["42", "🦀"]);
Full concurrency support. AtomicBloomFilter is a drop-in replacement for RwLock<OtherBloomFilter> because all methods take &self:
use fastbloom::AtomicBloomFilter;
let filter = AtomicBloomFilter::with_num_bits(1024).expected_items(2);
filter.insert("42");
filter.insert("🦀");
Bloom filters are space-efficient approximate membership set data structures supported by an underlying bit array to track item membership. To insert/check membership, a number of bits are set/checked at positions based on the item's hash. False positives from a membership check are possible, but false negatives are not. Once constructed, neither the Bloom filter's underlying memory usage nor number of bits per item change. See more.
hash(4) ──────┬─────┬───────────────┐
↓ ↓ ↓
0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 1 0
↑ ↑ ↑
└───────────┴───────────┴──── hash(3) (not in the set)
fastbloom is blazingly fast because it efficiently derives many index bits from only one real hash per item and leverages other research findings on Bloom filters. fastbloom employs "hash composition" on two 32-bit halves of an original 64-bit hash. Each subsequent hash is derived by combining the original hash value with a different constant using modular arithmetic and bitwise operations. This results in a set of hash functions that are effectively independent and uniformly distributed, even though they are derived from the same original hash function. Computing the composition of two original hashes is faster than re-computing the hash with a different seed. This technique is explained in depth in this paper.
Hashers used:
- xxhash: sbbf
- Sip1-3: bloom, bloomfilter, probabilistic-collections
- ahash: fastbloom
fastbloom does not compromise accuracy. Below is a comparison of false positive rates with other Bloom filter crates:
rand - Enabled by default, this has the DefaultHasher source its random state using thread_rng() instead of hardware sources. Getting entropy from a user-space source is considerably faster, but requires additional dependencies to achieve this. Disabling this feature by using default-features = false makes DefaultHasher source its entropy using getrandom, which will have a much simpler code footprint at the expense of speed.serde - BloomFilters implement Serialize and Deserialize when possible.loom - AtomicBloomFilters use loom atomics, making it compatible with loom testing.Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.