On Wed, Apr 5, 2017 at 2:29 PM <te...@segment.com> wrote: > What guarantees do Golang's timers (e.g. time.After, time.Sleep) provide? > If you're using *lots* of timers concurrently, what (if anything) could > cause them to misbehave (e.g. delay)? What are they bottlenecked by? > > > Most systems with really precise timing are not concurrent systems where you can run thousands or millions of goroutines or other concurrent work. There is a trade-off to be had here and getting to sub-millisecond precision under duress is not in general achievable unless you a priori plan your schedule.
I've said it before, but most systems that claims to do lower than sub-ms latency are really systems which are high throughput(put K exclamation marks here). They work by processing extremely fast and thus they have enough time to wait around, giving the impression that they are low latency. But disturb them a little, and you will realize they tend to be extremely sensitive in the upper pecentiles because of their properties. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
