Topic

trading systems

2026-09-30 · design note
From 1,623 µs to 129 µs: zero-copy SIMD wire streaming
A 5.7 MB binary wire block stream took 73 milliseconds to parse with standard MessagePack deserialization, one cost on an ingest thread reported to fall behind in market bursts. How SIMD search and fixed-point integers took per-block latency from 1,623 µs to 129 µs and throughput to 978 MB/s.
7 min
2026-09-26 · design note
ringfire: the ring itself, on the other machine
A market-data ring in /dev/shm now has identical copies on other hosts, same sequence numbers, same order: about 30 µs across a LAN by multicast, and 51.7 ms p99 across the Pacific with a clock offset good to a few milliseconds.
11 min
2026-09-19 · notes
Container up, data gone for four hours: silent failures in crypto market data collection
22 collectors on 15 exchanges (Binance, OKX, Bybit, Coinbase and more), 240,000 records per second, zero crashes all summer, and a dozen incidents where data vanished silently. Where to put the collector, what breaks without an error in the log, and which metrics give it away.
16 min
2026-09-16 · design note
rapidfire: the channel between a market feed and a decision
The hand-off between a market-data reader and a strategy loop is one of the few latencies in a trading process under our control. How we built a lock-free channel for it, what broke on a 128-core ARM box, and where the assembly landed.
7 min