Boost.Asio and Boost.Serialization, Part II
summary
Prototype message-passing runtime uses Boost.Asio and Boost.Serialization to send polymorphic actions over TCP, implements a zero-copy archive (two‑pass metadata + buffers) to avoid copies, and shows how to manage multiple outstanding writes with shared_ptr lifetimes. It documents practical tweaks: disabling TCP_NODELAY and delayed ACK interactions, using an io_service pool, and array/bitwise serialization tricks. Measured annoyances include up to 500 microsecond TCP delays and goals of millions of tasks per node per second.
AI-written summary · about
chapters (9)
- 0:00Start
- 9:17AM: Runtime Constructor
- 9:43AM: Hello World Action
- 10:30AM: Hello World Main
- 18:25Tips & Tricks
- 28:23Serialization: Bitwise Serialization
- 29:50Serialization: Array Optimizations
- 30:38Serialization: Exporting Templates
- 32:26Serialization: Portable Archives
related talks
35mBeyond JSON: Improving inter-app communication
05mSimple RPC Server for Database Access
37mLet's build our own message streaming platform
27mEvolution of serialization formats and usage in Go
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
55mBuilding an Extensible Type Serialization System Using Partial Template Specialization
40mPerformance Improvements
56mEverything is serialization