4 ms·
You can 100% write services with P999 < 20ms in go. Not even trying that hard. Go is entirely suitable for this kind of constraints, I dare say that's go's main
by fcantournet 5y ago
You can 100% write services with P999 < 20ms in go.
Not even trying that hard.
Go is entirely suitable for this kind of constraints, I dare say that's go's main target.
P99 < 1ms, that's when you're going to want to switch it up.
- sagichmal 5y agoDepending on workload, Go also does sub-1ms p99 pretty easily. I'm getting sub-1ms p99.9.
- torbital 5y agoWhat are the proposed solutions to get better than that? C/Rust code? Assembly?
- 35fbe7d3d5b9 5y agoGoing fast is one thing. Making a program that responds consistently is different, and there's a continuum of choices. The last time I read about Go's GC they targeted 500us and for tons of applications that's more than sufficient; for some, it's not. You could start with twiddling some of the GC knobs Go gives you, but you're still working against an SLO. If you need stronger guarantees you'll look at languages that completely eschew GC, because Go's GC still has STW bits. Climb the ladder further and you're reducing allocations, eventually avoiding any malloc() beyond what it takes to get an arena and doing your own bookkeeping. I've never been near the top of the ladder when you have hard real-time constraints, but I've heard it involves paying Wind River for VxWorks licenses ;)