This. I would call the optimization described on the article as "low-hanging fruit": if you don't have the right DB indices or you are not batching your operati

This. I would call the optimization described on the article as "low-hanging fruit": if you don't have the right DB indices or you are not batching your operations, you can find that kind of improvement easily, mostly just because your code was not following the "fast path". Still very useful article even if just to show how to use profiling tools, which you will need to even for much-higher-hanging fruit.