Abstract
Performance optimization is a skill that everyone wants on their resume today. It's an essential arrow in your quiver if you want to stand out from the average developer.
The goal is to make your software faster or use fewer resources.
Even if you don't care about it now, there may come a time when your software starts running slow, consuming too many resources, or getting killed by the dreaded OOM issue. Not knowing where to begin investigating, how to read the metrics, or how to fix the code could keep you awake at night. And usually, when performance optimization is needed, the situation is far from ideal. At that point, we either save the boat or sink it.
Misinterpreting the data can lead to missing the root cause of degradation or fixing the wrong part of the code, resulting in bugs, crashes, or even worse performance.
If you've ever been in this situation or want to know what to do if it happens, this session is for you.
Join me as we dive into profiling, tracing, benchmarking, Garbage Collection, and more. Let's explore what Go offers and how to optimize your software to serve billions of requests.
