Go provides very adequate profiling tools for debugging this type of problem. http://blog.golang.org/profiling-go-programs http://blog.golang.org/profiling-go-

Go provides very adequate profiling tools for debugging this type of problem. http://blog.golang.org/profiling-go-programs http://blog.golang.org/profiling-go-programs FWIW, I did `ab -n 1million -c 100` with your program on Windows/amd64 and memory grew from from 3.4MB to 3.9MB.