Profiling Go code is one of the best ways to determine where the bottlenecks are within your code base. We have physical limitations to our computer systems (CPU clock speed, memory size/speed, I/O read/write speeds, and network throughput, to give a few examples), but we can often optimize our programs to more efficiently utilize our physical hardware. After a profile of a computer program is taken with a profiler, a report is created. This report, often called a profile, can tell you information about the program that you ran. There are many reasons why you might want to understand the CPU and memory utilization of your program. A couple of examples are listed as follows:
CPU profiling reasons:
- Check performance improvements in new releases of software
- Validate how much CPU is being utilized for each task
- Limit CPU utilization in order to save money ...
