Golang’s most important feature is invisible

Re:Golang’s most important feature is invisible by technosamay20 on Sunday January 23, 2022 @03:44AM (#30044639)

Thanks for sharing this insight. Is this a issue with just the web server.

If I have a standalone task, which tires to use 128 cores and manages parallel tasks using goroutines communicating via channels - will I be able to successfully leverage 128 cores.

[ Parent | on HN ]

Re:Golang’s most important feature is invisible by jeffbee on Sunday January 23, 2022 @12:33PM (#30048177)

If your tasks are large enough to dominate, then the non-scalability of the goroutine scheduler and the network stack won’t be an issue. For example, if your task is compressing some huge hunk of a video and it takes a second to do it, then it will scale fine. Then again, you can get this scalability from anything, including `xargs`.

[ Parent | on HN ]