3 ms·
Using Go's profiling tool with its "source" view: I used "go tool pprof -http=: cpu.prof", where cpu.prof was generated by "go-1brc -cpuprofile=cpu.prof -revisi
by benhoyt 3y ago
Using Go's profiling tool with its "source" view: I used "go tool pprof -http=: cpu.prof", where cpu.prof was generated by "go-1brc -cpuprofile=cpu.prof -revision=9 measurements.txt".
- Beltalowda 3y agoCheers; I've always difficulty mapping those pprof graphs to actual concrete code and I never managed to get anything more useful out of it. This is the biggest take-away from this post to be honest; had no idea it could do anything like that. Sometimes it's the little things... You can get something similar with the CLI using: go tool pprof -weblist='mypkgname' cpu.out # Generate HTML and open go tool pprof -list='mypkgname' cpu.out # Generate text to stdout