Executors in C++
summary
Standalone proposals compete: one exposes three entry points dispatch/post/defer, another collapses to a single templated spawn. Committee drops the original executor design from the concurrency TS, but implementers already build concrete systems: a real-time executor that spawns OS threads and sets priorities, and a concentrator that asks tasks for their executor so different pipeline stages run on different executors. The demos compile and run and expose usability and deadlock pitfalls.
AI-written summary · about
chapters (22)
- 0:00Start
- 1:11Motivation async
- 4:25Layers
- 5:42Proposal History 2
- 8:47Abstract Base Class
- 9:17Threads
- 13:36Progress Guarantees
- 15:33Destructor
- 17:06thread pool
- 20:23loop executor
- 24:14Parallel Algorithms
- 24:40Generic Task Managers
- 25:06Realtime Priority
- 26:18Cyclic Realtime Tasks
- 27:56Data Concentrator
- 28:52Proposal History 3
- 33:32Executors and Async Ops
- 47:13Executors and Schedulers, R4
- 51:37task wrapper Deadlock
- 52:25Wrap Up
- 53:20Executors Dilemma
- 53:55Questions
related talks
01h 00mDeciphering C++ Coroutines Part 2 - Mastering Asynchronous Control Flow
20mNode and Libuv and Strongloop
22mBun, Deno, Node.js? Recreating a JavaScript runtime from Scratch
30mParallel Universes: Node.js
40mIt's Not Just Node.js Anymore
13mConcurrency vs Parallelism in Node.js: Understanding the Event Loop & Worker Threads
28mBryan Hughes - SeattleJS Conference 2017
34mWorker Threads vs C ++ Addons (part 2)