Network overhead, not the order book, is the bottleneck
LOB processing alone: p50 ~50ns / p99 ~280ns Full RTT: p50 ~16.1µs / p99 ~22.8µs -> 16.3µs of 16.4µs median RTT is loopback TCP + kernel scheduling
Arjun Prabhakaran — CS grad, Bengaluru
“software that can’t afford to lose a race condition, or an argument with the profiler.”
I build low-latency trading infrastructure and quantitative research tools — order books, kernel-bypass feed handlers, and alpha signals — and publish the real benchmark numbers, good and bad.
SEE CURRENT STATUSSelected practice
This is a running record, not a highlight reel: experiments that start as questions, get instrumented, and turn into benchmarks, models, parsers, and working prototypes — logged as they happen.
Current status
Six projects, three tiers of done. Nothing here is marked finished until it's been measured.
Shipped & benchmarked
In progress
On the bench
Current boundary: ~16µs of loopback TCP/kernel overhead is the floor without kernel bypass — DPDK or RDMA is the next thing worth measuring.
Selected findings
Pulled straight from the devlogs, not cleaned up after the fact.
Network overhead, not the order book, is the bottleneck
LOB processing alone: p50 ~50ns / p99 ~280ns Full RTT: p50 ~16.1µs / p99 ~22.8µs -> 16.3µs of 16.4µs median RTT is loopback TCP + kernel scheduling
Isolation helped the tail, not the median
Untuned: mean RTT 16.36µs, max 88.27µs Full isolation: mean RTT 22.64µs, max 52.25µs -> traded median latency for tail predictability
Real NASDAQ ITCH feed, parsed clean on the first run
109,386,091 messages parsed 3,280,036,325 / 3,280,036,325 bytes consumed 8,909 distinct symbols identified
Strongest signal across 15 tickers, 90-day backtest
PLTR IC(1d) = +0.352, p<0.01, 64.3% hit rate GME +0.215 (p<0.05) · NVDA +0.168 · MSFT +0.167 TSLA came back negative at -0.183
Selected work
Loading index...
Get in touch