> Your bottleneck is most likely not CPU or Python itself. I've found that this is often the case. Nearly always disk or network. But it's sometimes surprisi

> Your bottleneck is most likely not CPU or Python itself. I've found that this is often the case. Nearly always disk or network. But it's sometimes surprising how little work you need to do to become CPU-bound. This is the price we pay for such a tremendously dynamic language. Indeed, the article's suggestions of C/Cython/PyPy are good ones to remedy the problem when it occurs.