Finding Hidden Bottlenecks in Go Apps: A Lazy, Hacky, and Bruteforce Method
go
dev.to
When developing pgrwl - a PostgreSQL WAL receiver - performance is a critical concern. Every part of the program must be predictable. There should be no hidden bottlenecks. But what about: typos that silently degrade performance? missing tests that fail to catch inefficiencies? slow logic introduced "just for now"? accidental O(n^2) behavior? These issues are often hard to detect. The Problem For instance, you may concatenate a huge template in a loop, but that may be done o