Making a Go program faster with a one-character change
1–10 of 249 posts
Re: Making a Go program faster with a one-character change
#21 character, in 2 places ;) I did not know profiling support for go was so seamless, thank you!
May I ask, is that theme custom or available somewhere? I really enjoyed it
Re: Making a Go program faster with a one-character change
#3That seems like a potential for compiler optimization. It should already know that the rule value is only used one time, as the target of a & and this must be somewhat common in managing return values.
Re: Making a Go program faster with a one-character change
#4Thank you for sharing. I'm curious if you would recommend any good resources for profiling with Go. I enjoyed your code snippets and methodology.
Re: Making a Go program faster with a one-character change
#5> You can see these decisions being made by passing -gcflags=-m to go build:
That's a very nice feature! I wonder if compilers for other languages have something similar.
Re: Making a Go program faster with a one-character change
#6Went from 4.139s to 2.413s. I fail to see how it is 70%. I think it is explained as 4.139/2.413 = 1.7 which of course doesn't make sense here.
Re: Making a Go program faster with a one-character change
#7That seems like a potential for compiler optimization. It should already know that the rule value is only used one time, as the target of a & and this must be somewhat common in managing return values.
[deleted]
Re: Making a Go program faster with a one-character change
#8Went from 4.139s to 2.413s. I fail to see how it is 70%. I think it is explained as 4.139/2.413 = 1.7 which of course doesn't make sense here.
It would probably be more accurate to say it can do 70% more stuff in the same time. Or that it takes 42% less runtime
Re: Making a Go program faster with a one-character change
#91 character, in 2 places ;) I did not know profiling support for go was so seamless, thank you! May I ask, is that theme custom or available somewhere? I really enjoyed it
> 1 character, in 2 places ;)
Moving a single character from one place to another. :-)
A good explanation of why "fire the developers with the lowest 50% of lines added" is an idiotic thing to do: this sort of deep analysis takes a lot of time and expertise, and frequently results in tiny changes.
Re: Making a Go program faster with a one-character change
#10Went from 4.139s to 2.413s. I fail to see how it is 70%. I think it is explained as 4.139/2.413 = 1.7 which of course doesn't make sense here.
This is an extremely common mistake in reporting performance numbers. That the old version is 70% slower does not make the new version 70% faster.