GolangEnglish · 2 days ago

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

2

cross-posted to:
[email protected]

5

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

GolangEnglish · 2 days ago

2

cross-posted to:
[email protected]

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

Laser@feddit.org
link
fedilink
arrow-up
1·
1 day ago
50000 Goroutine! Holy fuck that’s a lot of Goroutine.

It really is dumb AI slop
breakingcups@lemmy.world
link
fedilink
arrow-up
1·
2 days ago
Oof, that is definitely AI-written.

Golang

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: [email protected]

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.

1 user / day
19 users / week
57 users / month
201 users / 6 months
614 local subscribers
2.61K subscribers
255 Posts
373 Comments
Modlog