I love profiling! There's a whole lot of different profiling tools available, and they provide a treasure trove of information. If you roughly know the slow area of the code, it's usually not a problem to understand why it is slow. What I have trouble with though, is quickly identifying the rough point of interest. Today I am pretty good at trisecting performance issues, and, if I make it a mission to identify the bottleneck, I usually manage to do it in a couple of hours. However, I don't kn...