DoorDash's search platform team investigated CPU utilization variance and latency spikes in their searcher pods. Through deep profiling using perf stat and flame graphs, they discovered that Shenandoah GC's memory barriers in JIT-compiled code were causing significant overhead in hot Lucene functions. Switching to G1GC and

8m read timeFrom careersatdoordash.com
Post cover image
Table of contents
The problem: High variance in Searcher CPU utilizationInvestigationStay Informed with Weekly UpdatesPlease enter a valid email address.Thank you for Subscribing!ResultsConclusionAcknowledgements

Sort: