|
|
|
|
|
|
by _cenw
1032 days ago
|
|
|
Go can have unexpected performance differences way higher up in the stack. Ask me about that one time I optimized code that was deadlocking because the Go compiler managed to not insert a Gosched[1] call into a loop transforming data that took ~30 minutes or so. The solution could've been to call Gosched, but optimizing the loop to a few seconds turned out to be easier. I assume the inverse - the go compiler adding too many Goscheds - can happen too. It's not that expensive - testing a condition - but if you do that a few million times, things add up. [1]: https://pkg.go.dev/runtime#Gosched |
|
|