An interesting post on a performance hit that occurred on Drupal 7.33 where the symptoms are CPU’s running at 100%.
After deployment to live, we got some reports that the site was responding slow. … We had to investigate after a while as there was no sign of improvement, the CPU of the server was hitting 100% 24/7. Jeroen Bobbeldijk
If you’re upgrading to 7.33 and are finding yourself in a pickle with maxed out CPU’s, you can profile the module_load_include() function as a probably cause.
It goes to show how a change in a seemingly unrelated part of the code can have tremendous impact on other parts. And linking them together isn’t always as easy as it looks.
Nice find!