codeinabox@programming.dev to

Golang@programming.devEnglish · 4 hours ago

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

2

cross-posted to:
lobsters

5

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

codeinabox@programming.dev to

Golang@programming.devEnglish · 4 hours ago

2

cross-posted to:
lobsters

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 register to comment.

Chat

Laser@feddit.org
link
fedilink
arrow-up
1·
1 hour 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·
3 hours ago
Oof, that is definitely AI-written.

Golang@programming.dev

golang@programming.dev

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.

6 users / day
16 users / week
53 users / month
194 users / 6 months
1 local subscriber
2.61K subscribers
134 Posts
110 Comments
Modlog