News for hackers. Stuff that matters.

A comment on Go Creeping In. Parent comment

Re:Go Creeping In by pcwalton on Tuesday June 18, 2019 @11:46AM (#20214368)
Do many Go programs really have 100,000 goroutines simultaneously? I'm certain that's quite rare.
[ Parent | on HN ]
Re:Go Creeping In by stickupkid on Tuesday June 18, 2019 @01:08PM (#20215405)
Working as part of Juju project, I can tell you for certain that the answer here is yes, very much so.
[ Parent | on HN ]
Re:Go Creeping In by pcwalton on Tuesday June 18, 2019 @03:48PM (#20217605)
If you have over 100,000 threads, then you are at the point of scalability where you probably want more than what Go can provide. Async I/O would likely be better for your use case, because even 2kB of stack per thread is 195MB just from thread stacks.
[ Parent | on HN ]
Re:Go Creeping In by saturn_vk on Tuesday June 18, 2019 @01:03PM (#20215328)
Well, even if you do not do any parallel work for each request in your service, each request in itself is a goroutine. So depending on the load of that service, you might reach such numbers, and more.
[ Parent | on HN ]