i’m all the time pushing for efficiency of golang and located plenty of areas whereby go is slower than c equal at 2x and 1.2x and so forth however questioning what’s the theoretical / sensible restrict of golang. particularly in multi core (448 cpu core) setting and so forth.
i’ve been utilizing utilizing go for the previous 6 years each day and with excessive effectivity consideration solely going for zero alloc stuff however i’m questioning how far am i able to push golang earlier than i have to all the time have a look at c / c++ / rust.
in an “unrelated difficulty”, that is my ideas on this assertion:
“Don’t talk by sharing reminiscence, share reminiscence by speaking.” (relevant solely as much as 16 core cpu programs, something greater than that gives you diminishing returns based mostly on how golang does thread scheduling… and so forth.)
any opinion / feedback on the difficulty title? not trolling however i really like golang simply that i’m all the time restricted by the effectivity of it. please dont counsel goasm. i do hope for a zero alloc cgo with out ffi overhead. unsure if this can be made potential.
C/C++ supply finer-grained management over reminiscence administration and {hardware} interactions, probably main to raised theoretical efficiency for very particular duties. It’s because C/C++ permit for direct manipulation of reminiscence addresses, which Go avoids for security causes.
