High-Performance gRPC Beyond HTTP/2
summary
Gama implements go-gRPC + Homa + HTTP/3 to run HTTP/2, HTTP/3 and raw Homa side-by-side on the same port, adds a 5‑byte Homa wire header and a TLS layer for Homa, and requires an upstreamed Homa kernel module and firewall hijack for production. Benchmarks on two bare‑metal machines with 1.5KB–3KB payloads (ping‑pong and pipelined) show unary P99 of 192 µs vs HTTP/2 541 µs, sustained ~160 TPS, and roughly 2–3× P99 improvements for Homa on low‑latency datacenter links.
AI-written summary · about
chapters (21)
- 0:00Introduction to talk
- 1:06Multi-protocol transaction paths
- 2:10GMA transport adapter framework
- 3:14HTTP/2 trade-offs and head-of-line blocking
- 5:24HTTP/3 and HOMA protocol benefits
- 7:10GMA architecture and protocol support
- 8:13Custom wiring formats for HOMA
- 9:39Demo setup and protocol port sharing
- 11:01Benchmarking methodology and test modes
- 12:25Demo results and performance metrics
- 13:58Concurrency test results
- 15:54High concurrency mixed payload results
- 17:20Steps to try GMA in your system
- 17:42Conclusion and Q&A introduction
- 18:24Q&A: Language and HOMA buffering
- 20:15Q&A: HOMA kernel and deployment
- 21:41Q&A: Protocol fit and network characteristics
- 23:12Q&A: Pluggable transports in gRPC
- 24:34Q&A: HOMA thread handling and UDP issues
- 26:21Q&A: Message size relevance to HOMA
- 27:23Q&A: HOMA adoption growth
