Rust at Sentry: 7 Years Later
summary
Seven years of running Rust at Sentry yields concrete outcomes: Rust handles source maps, symbolication for profiles and an ingestion relay that keeps ~1% of traces; many fixes land upstream in crates like gimli and pdb via Cargo; Python extension strategy moves from CFFI to PyO3 and Maturin; switching from Actix to raw Tokio improves backpressure handling. Surprising numbers: a boxed error gives ~25% speedup in one hot loop and a bad string clone bug becomes ~100000× slower in a pathological case. actual claim: Rust reduced runtime and ops pain tools used: PyO3 Maturin Cargo Tokio Relay
AI-written summary · about
chapters (12)
- 0:00Seven years of Rust at Sentry
- 2:29Sentry and Rust fit
- 4:34Why Rust over Python and C++
- 7:04Rust with Python runtime
- 9:09Rust stability and maintenance
- 10:10Evolving Python with Rust
- 13:41Unexpected Rust wins
- 16:26Rust performance pitfalls
- 21:17String handling mistakes in Rust
- 23:43Async challenges with Tokio
- 27:35Actix to Tokio migration
- 31:46Rust’s future and community
