Open-source implementation of the disruptor architecture in the previously-linked LMAX article.

A single-threaded transaction-processing system that punts all I/O to the outer edges to isolate the parts of the program that must operate concurrently.

A Python implementation of actor-in-a-thread, like Ruby's Celluloid. Named like Scala's Akka.

Quick reference to the relevant kernel parameters that need tuning to accept hundreds of thousands of TCP connections on single commodity instances.

Old but good bit from Brewer demonstrated a good thread implementation is able to handle as much concurrency as a good evented program. Bonus: Russ Cox, now working on Go, is acknowledged for his assistance.

Goals for the Intel Cilk GCC branch.

I'm guilty of conflating the terms "concurrency" and "parallelism." This article is more clear than most about the precise difference.

Interesting different take on concurrency in Python.

Back at it, this time with a beast of a server, a dataset that won't fit in memory (joy of joys!) and (inexplicably) more OCaml.