| josephine | dashmap | |
|---|---|---|
| 2 | 12 | |
| 64 | 2,739 | |
| - | - | |
| 0.0 | 5.1 | |
| almost 4 years ago | 25 days ago | |
| Rust | Rust | |
| Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
josephine
-
Samsara, a safe Rust concurrent cycle collector
It turned out that attempts at finding the “small set of hooks” needed to make arbitrary garbage-collectors works with Rust were never really successful, even though there have been lots of attempts by people at Mozilla, since it was of primary importance for the integration with the DOM in servo. The last one I'm aware being this which scope was much narrower than what the pcwalton was envisioning when he wrote this post you haven't read but definitely should.
-
A Tour of Safe Tracing GC Designs in Rust
For me, the most interesting one is Josephine[1]. This allows tracking of stack roots, doesn't limit the time when GC can run, and takes advantage of rust affine type system. However I have to say the API feels fairly clunky, with the need to root everything before mutation and the need to pass context objects to every method.
[1] https://github.com/asajeffrey/josephine
dashmap
- StupidAlloc: what if memory allocation was bad actually
-
dashmap VS scalable-concurrent-containers - a user suggested alternative
2 projects | 13 Apr 2023
-
Samsara, a safe Rust concurrent cycle collector
The problem is, every single one of these half-dozen crates has at least one known major issue (including UAF), exactly like C++ implementations (which isn't surprising since it's the kind of things where the ownership isn't clear and then the borrow checker can't help us).
-
Rust vs Go
Deadlocks and leaks are easy as other languages.
-
Shared mutable state is bad... so how do I create a global cache in a multi-threaded app?
Have you considered https://github.com/xacrimon/dashmap ?
-
Announcing Leapfrog, a faster concurrent HashMap
Dashmap made some api changes compared to the stdlibs hashmap, which leads to some oddities, as highlighted here: https://github.com/xacrimon/dashmap/issues/175
-
Writing a concurrent LRU cache
Some additional notes are in this slide deck and the implementation javadoc. You'd probably want to use something like DashMap for the hash table.
-
HashMap-based cache for async programs
You can look at existing concurrent maps like Dashmap https://github.com/xacrimon/dashmap or Cashmap https://gitlab.redox-os.org/redox-os/chashmap
-
How does one avoid lock of locks? or use the technique of latch crabbing of databases
Also dashmap
-
Noteworthy concurrent data structures?
The only one I've used is Dashmap, it's a concurrent interior-mutability hashmap. Very convenient crate in the case you need that.
What are some alternatives?
hashbrown - Rust port of Google's SwissTable hash map
moka - A high performance concurrent caching library for Rust
HashMap - An open addressing linear probing hash table, tuned for delete heavy workloads
crossbeam - Tools for concurrent programming in Rust
leapfrog - Lock-free concurrent and single-threaded hash map implementations using Leapfrog probing. Currently the highest performance concurrent HashMap in Rust for certain use cases.
megahash - A super-fast C++ hash table with Node.js wrapper, tested up to 1 billion keys.
stretto - Stretto is a Rust implementation for Dgraph's ristretto (https://github.com/dgraph-io/ristretto). A high performance memory-bound Rust cache.
sharded - Safe, fast, and obvious concurrent collections in Rust.
im-rs - Assorted immutable collection datatypes for Rust
rudy - A MITM proxy written in Rust
concurrentlinkedhashmap - A ConcurrentLinkedHashMap for Java
ristretto - A high performance memory-bound Go cache