Experimenting with Go build I worked on this experiment with Go on GitHub Codespace.
Have a look! Here is our statement of problem.
go test -bench main_test.go -vYou will notice that
=== RUN Test_computeEuler
=== RUN Test_computeEuler/empty
--- PASS: Test_computeEuler (4.19s)
--- PASS: Test_computeEuler/empty (4.19s)
=== RUN Test_computeBeastEuler
=== RUN Test_computeBeastEuler/empty
--- PASS: Test_computeBeastEuler (2.51s)
--- PASS: Test_computeBeastEuler/empty (2.51s)
PASS
ok go-beast-demo 6.705sThe beast Euler is twice faster than the normal function. The trick is that we reduce the number of iterations to calculate e^5. The solution is just move it up to the outermost iteration and pass it through the innermost loop.
Anyway, this should be detected by the compiler. You can build it like this
go build main.go
time ./main
{133 110 84 27 144}
real 0m4.371s
...
We want the following binary to run as fast like the beast Euler one.
Here is what it looks
go build -gcflags=-m main.go
# command-line-arguments
./main.go:18:6: can inline intPow
./main.go:32:19: inlining call to intPow
./main.go:34:20: inlining call to intPow
./main.go:36:21: inlining call to intPow
./main.go:38:22: inlining call to intPow
./main.go:39:22: inlining call to intPow
./main.go:58:36: inlining call to errors.New
./main.go:63:18: inlining call to intPow
./main.go:65:19: inlining call to intPow
./main.go:67:20: inlining call to intPow
./main.go:69:21: inlining call to intPow
./main.go:71:22: inlining call to intPow
./main.go:89:36: inlining call to errors.New
./main.go:95:14: inlining call to fmt.Println
./main.go:99:13: inlining call to fmt.Println
./main.go:58:36: &errors.errorString{...} escapes to heap
./main.go:89:36: &errors.errorString{...} escapes to heap
./main.go:95:14: ... argument does not escape
./main.go:99:13: ... argument does not escape
./main.go:99:13: solution escapes to heapMove to your local machine. We will try using the gccgo. Just follow this link https://go.dev/doc/install/gccgo#Prerequisites If anything went wrong, just
cd gccgo
./contrib/download_prerequisites
It will only works in Linux, but not Mac(gccgo is not working on Darwin) Anyway, we can run this on cloud.
docker compose build
docker run -it go-beast-mode_app bash
So far, we can try to benchmark it
root@41b455a23e1b:/go/app# time ./optimized
INFO[0000] {133 110 84 27 144}
INFO[0000] hello world
INFO[0000] hello world
real 0m0.585s
user 0m0.571s
sys 0m0.004s
Keep in mind that, sometimes it is not about the compiled program itself. But, the way you build your architecture created a bottleneck which required other approaches.
If something went wrong, try
docker compose down --remove-orphans