While it might seem "the hard way" to a developer who deals with db performance just occasionally, it's a regular performance tuning workflow. The problem and the solution in this case was fairly simple.

Nevertheless, nice writeup.