September 2015
Intermediate to advanced
198 pages
4h 52m
English
We discussed in previous chapters that random performance tuning of code rarely works, because we may not be tuning in the right place. It is crucial to find the performance bottlenecks before we can tune those areas in the code. Upon finding the bottleneck, we can experiment with alternate solutions around it. In this section we will look into finding the bottlenecks.
Latency is the starting, and the most obvious, metric to drill-down in order to find bottlenecks. For Clojure code, we observed in Chapter 6, Measuring Performance that code profiling tools can help us find the areas of bottleneck. Profilers are, of course, very useful. Once you discover hotspots via profilers, ...
Read now
Unlock full access