News for hackers. Stuff that matters.

A comment on Size visualization of Go executables using D3. Parent comment

Re:Size visualization of Go executables using D3 by j16sdiz on Tuesday April 02, 2019 @06:04AM (#19552497)
It is not as slow as it sounds.

golang do heavy inline-ing and most of its performance comes from concurrency. Putting values on stack actually make concurrency easier.

That said, there is a proposal to do it in register: https://github.com/golang/go/issues/18597 It is challenging and not in high priority. The current priority is do more inlining.

[ Parent | on HN ]
Re:Size visualization of Go executables using D3 by 1_000_000 on Tuesday April 02, 2019 @12:08PM (#19555610)
> "It is not as slow as it sounds."

Yes, it is. 5%-10% in the very link you posted.

> "golang do heavy inline-ing"

No, it does not. See https://github.com/golang/go/issues/17566

> "most of its performance comes from concurrency"

That's just ridiculous. They didn't write all crypto and math in assembly just for nothing. Lumping bunch of slow function calls onto several threads is not where performance magically comes from. And you are confusing concurrency and parallelism.

[ Parent | on HN ]
Re:Size visualization of Go executables using D3 by pcwalton on Tuesday April 02, 2019 @10:35AM (#19554497)
> Putting values on stack actually make concurrency easier.

Could you elaborate how?

[ Parent | on HN ]