In this 2-part blog we’ll take a look at how I used the go profiling and built-in benchmarking tools to optimize a naive ray-tracer written in Go.
Using pprof to identify bottlenecks.
Reducing allocations and Caching.
Conclusion of part 1.
(Note: Most of this blog post is based on using Go 1.13)
The full source code for my little ray-tracer can be found here: https://github.com/eriklupander/rt.