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

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

Comments

breakingcups 1 point 9 months ago

Oof, that is definitely AI-written.

path: 0 21570114, hotness: undefined, score: 1, children: 0

Laser 1 point 9 months ago

50000 Goroutine! Holy fuck that's a lot of Goroutine.

It really is dumb AI slop

path: 0 21571289, hotness: undefined, score: 1, children: 0

@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.

go to feed...

@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.

go to feed...