When Concurrency Matters: Behaviour-Oriented Concurrency
summary
Behaviour-Oriented Concurrency (BoC) introduces cones as exclusive shared-data owners, behaviors as spawned units that declare required cones, and a single when primitive that atomically schedules multi-cone work into a DAG to guarantee deadlock freedom and ordering. The authors provide a formal semantics, a reusable C++ runtime artifact, and Savina-benchmark results showing many cases with >20% speedups versus Pony and overall comparable performance; a banking example removes actor messaging overhead and scales well across hardware threads.
AI-written summary · about
chapters (10)
- 0:00Behavior-Oriented Concurrency intro
- 0:22Why concurrency matters
- 1:47Desired properties
- 3:33What is BOC
- 5:19Abstract execution
- 7:27Formal semantics
- 8:10B performance
- 10:14Research paper expectations
- 10:56Conclusion
- 11:58Q&A
related talks
25mConcurrency-aware object-oriented programming with roles
01h 35mThinking Outside the Synchronisation Quadrant
01h 21mStructured Concurrency
01h 16mConcurrency Approaches: Past, Present, and Future
39mLet's talk concurrency
45mPony for Safe, Fast, concurrent programs
54mStructured Concurrency: Hierarchical Cancellation & Error Handling
01h 16mDesigning for C++ Concurrency Using Message Passing