From 54fdd0c72537d17b7a3de9b6460108d6baaf4364 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Sun, 17 Jan 2021 19:37:25 +0100 Subject: [PATCH] goroutines, they're crazy --- goroutine.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/goroutine.md b/goroutine.md index 96c129f..a80fb37 100644 --- a/goroutine.md +++ b/goroutine.md @@ -17,7 +17,7 @@ All Goroutine profiling available in Go requires an `O(N)` **stop-the-world** ph As a rule of thumb, applications that are extremely latency sensitive and make use of thousands of active goroutines might want to be a little careful with goroutine profiling in production. That being said, large number of goroutines, and perhaps even Go itself, might not be good idea for such applications to begin with. -Most applications that can tolerate a few ms of ocassional extra latency should have no issues with continous goroutine profiling in production. +Most applications that don't spawn crazy amounts of goroutines and can tolerate a few ms of ocassional extra latency should have no issues with continous goroutine profiling in production. ## Goroutine Properties