Concurrent Ruby

Modern concurrency tools for Ruby. Inspired by Erlang, Clojure, Scala, Haskell, F#, C#, Java, and classic concurrency patterns.

The design goals of this gem are:

Be an 'unopinionated' toolbox that provides useful utilities without debating which is better or why
Remain free of external gem dependencies
Stay true to the spirit of the languages providing inspiration
But implement in a way that makes sense for Ruby
Keep the semantics as idiomatic Ruby as possible
Support features that make sense in Ruby
Exclude features that don't make sense in Ruby
Be small, lean, and loosely coupled

Supported Ruby versions

MRI 1.9.3, 2.0 and above, JRuby 1.7x in 1.9 mode, JRuby 9000, and Rubinius 2.x are supported. This gem should be fully compatible with any interpreter that is compliant with Ruby 1.9.3 or newer. Java 8 is preferred for JRuby but every Java version on which JRuby 9000 runs is supported.

Thread Safety

Concurrent Ruby makes the strongest thread safety guarantees of any Ruby concurrency library. We are the only library with a published memory model which provides consistent behavior and guarantees on all three of the main Ruby interpreters (MRI/CRuby, JRuby, and Rubinius).

Every abstraction in this library is thread safe. Similarly, all are deadlock free and many are fully lock free. Specific thread safety guarantees are documented with each abstraction.

It is critical to remember, however, that Ruby is a language of mutable references. No concurrency library for Ruby can ever prevent the user from making thread safety mistakes (such as sharing a mutable object between threads and modifying it on both threads) or from creating deadlocks through incorrect use of locks. All the library can do is provide safe abstractions which encourage safe practices. Concurrent Ruby provides more safe concurrency abstractions than any other Ruby library, many of which support the mantra of "Do not communicate by sharing memory; instead, share memory by communicating". Concurrent Ruby is also the only Ruby library which provides a full suite of thread safe and immutable variable types and data structures.

Features & Documentation

The primary site for documentation is the automatically generated API documentation

We also have a mailing list and IRC (gitter).

General-purpose Concurrency Abstractions

Async: A mixin module that provides simple asynchronous behavior to a class. Loosely based on Erlang's gen_server.
Future: An asynchronous operation that produces a value.
- Dataflow: Built on Futures, Dataflow allows you to create a task that will be scheduled when all of its data dependencies are available.
Promise: Similar to Futures, with more features.
ScheduledTask: Like a Future scheduled for a specific future time.
TimerTask: A Thread that periodically wakes up to perform work at regular intervals.

Thread-safe Value Objects, Structures, and Collections

Collection classes that were originally part of the (deprecated) thread_safe gem:

Array A thread-safe subclass of Ruby's standard Array.
Hash A thread-safe subclass of Ruby's standard Hash.
Set A thread-safe subclass of Ruby's standard Set.
Map A hash-like object that should have much better performance characteristics, especially under high concurrency, than Concurrent::Hash.
Tuple A fixed size array with volatile (synchronized, thread safe) getters/setters.

Value objects inspired by other languages:

Maybe A thread-safe, immutable object representing an optional value, based on Haskell Data.Maybe.
Delay Lazy evaluation of a block yielding an immutable result. Based on Clojure's delay.

Structure classes derived from Ruby's Struct:

ImmutableStruct Immutable struct where values are set at construction and cannot be changed later.
MutableStruct Synchronized, mutable struct where values can be safely changed at any time.
SettableStruct Synchronized, write-once struct where values can be set at most once, either at construction or any time thereafter.

Thread-safe variables:

Agent: A way to manage shared, mutable, asynchronous, independent state. Based on Clojure's Agent.
Atom: A way to manage shared, mutable, synchronous, independent state. Based on Clojure's Atom.
AtomicBoolean A boolean value that can be updated atomically.
AtomicFixnum A numeric value that can be updated atomically.
AtomicReference An object reference that may be updated atomically.
Exchanger A synchronization point at which threads can pair and swap elements within pairs. Based on Java's Exchanger.
MVar A synchronized single element container. Based on Haskell's MVar and Scala's MVar.
ThreadLocalVar A variable where the value is different for each thread.
TVar A transactional variable implementing software transactional memory (STM). Based on Clojure's Ref.

Java-inspired ThreadPools and Other Executors

See the thread pool overview, which also contains a list of other Executors available.

Thread Synchronization Classes and Algorithms

CountDownLatch A synchronization object that allows one thread to wait on multiple other threads.
CyclicBarrier A synchronization aid that allows a set of threads to all wait for each other to reach a common barrier point.
Event Old school kernel-style event.
IVar Similar to a "future" but can be manually assigned once, after which it becomes immutable.
ReadWriteLock A lock that supports multiple readers but only one writer.
ReentrantReadWriteLock A read/write lock with reentrant and upgrade features.
Semaphore A counting-based locking mechanism that uses permits.

Edge Features

These are available in the concurrent-ruby-edge companion gem.

These features are under active development and may change frequently. They are expected not to keep backward compatibility (there may also lack tests and documentation). Semantic versions will be obeyed though. Features developed in concurrent-ruby-edge are expected to move to concurrent-ruby when final.

Promises Framework: Unified implementation of futures and promises which combines features of previous Future, Promise, IVar, Event, dataflow, Delay, and TimerTask into a single framework. It extensively uses the new synchronization layer to make all the features non-blocking and lock-free, with the exception of obviously blocking operations like #wait, #value. It also offers better performance.
Actor: Implements the Actor Model, where concurrent actors exchange messages.
Channel: Communicating Sequential Processes (CSP). Functionally equivalent to Go channels with additional inspiration from Clojure core.async.
LazyRegister
AtomicMarkableReference
LockFreeLinkedSet
LockFreeStack

Statuses:

Why are these not in core?

Promises Framework - They are being finalized to be able to be moved to core. They'll deprecate old implementation.
Actor - Partial documentation and tests; depends on new future/promise framework; stability is good.
Channel - Brand new implementation; partial documentation and tests; stability is good.
LazyRegister - Missing documentation and tests.
AtomicMarkableReference, LockFreeLinkedSet, LockFreeStack - Need real world battle testing.

Usage

Everything within this gem can be loaded simply by requiring it:

require 'concurrent'

To use the tools in the Edge gem it must be required separately:

require 'concurrent-edge'

If the library does not behave as expected, Concurrent.use_stdlib_logger(Logger::DEBUG) could help to reveal the problem.

Installation

gem install concurrent-ruby

or add the following line to Gemfile:

gem 'concurrent-ruby', require: 'concurrent'

and run bundle install from your shell.

Edge Gem Installation

The Edge gem must be installed separately from the core gem:

gem install concurrent-ruby-edge

or add the following line to Gemfile:

gem 'concurrent-ruby-edge', require: 'concurrent-edge'

and run bundle install from your shell.

C Extensions for MRI

Potential performance improvements may be achieved under MRI by installing optional C extensions. To minimize installation errors the C extensions are available in the concurrent-ruby-ext extension gem. concurrent-ruby and concurrent-ruby-ext are always released together with same version. Simply install the extension gem too:

gem install concurrent-ruby-ext

or add the following line to Gemfile:

gem 'concurrent-ruby-ext'

and run bundle install from your shell.

In code it is only necessary to

require 'concurrent'

The concurrent-ruby gem will automatically detect the presence of the concurrent-ruby-ext gem and load the appropriate C extensions.

Note For gem developers

No gems should depend on concurrent-ruby-ext. Doing so will force C extensions on your users. The best practice is to depend on concurrent-ruby and let users to decide if they want C extensions.

lpradovera/concurrent-ruby

Concurrent Ruby

Supported Ruby versions

Thread Safety

Features & Documentation

General-purpose Concurrency Abstractions

Thread-safe Value Objects, Structures, and Collections

Java-inspired ThreadPools and Other Executors

Thread Synchronization Classes and Algorithms

Edge Features

Statuses:

Usage

Installation

Edge Gem Installation

C Extensions for MRI

Note For gem developers

Maintainers

Special Thanks

License and Copyright