Finding and Fixing a 50,000 Goroutine Leak That Nearly Killed Production

skoredin.pro

Finding and Fixing a 50,000 Goroutine Leak That Nearly Killed Production

skoredin.pro

codeinabox@programming.dev to

Golang@programming.devEnglish · 1 month ago

Memory usage: 47GB. Response time: 32 seconds. Goroutines: 50,847. The story of debugging and fixing a massive goroutine leak in production.

cross-posted from: https://lemmy.bestiver.se/post/862879

Comments

You must log in or # to comment.

Chat

Golang@programming.dev

golang@programming.dev

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !golang@programming.dev

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

17 users / day
17 users / week
17 users / month
17 users / 6 months
1 local subscriber
2.64K subscribers
50 Posts
0 Comments
Modlog