I’m sorry to hear you’ve run into issues.
Could you try to deactivate Jetpack modules under Jetpack > Settings, one module at a time, and let me know if the problem seems to be related to one specific module?
Thanks!
Thread Starter
iPad Guy
(@patricklevellnet)
Hi Jeremy,
In order to do that, I would need to re-apply the 3.5 upgrade.
The best that I can do is tell you the modules that I had running, which were the following:
- Likes
- Notifications
- Related Postes
- Sharing
- Subscriptions
- WordPress.com Stats
Thanks.
Do you use the same modules right now, or have you deactivated some of them?
Thread Starter
iPad Guy
(@patricklevellnet)
Yes, I use those modules and a few others, like Mobile Themes, Publicize, Shortcode Embeds, Site Verification, and WP.me Shortlinks.
Even with these running in 3.4.3, CPU usage appears to be less than half of 3.5.
In this chart, I reactivated JetPack 3.5 shortly after 9:00, with only the previously mentioned modules running. I rolled it back to 3.4.3 shortly after 14:00. Nothing else changed on the site during that time.
Thanks.
Thanks for the extra details!
Out of the 6 modules you mentioned above, we’ve made changes to Related Posts, Sharing, Subscriptions, and Stats in 3.5. The problem must be coming from one of these modules. Unfortunately, I can’t spot anything obvious from looking at our changes.
Would you mind trying to re-apply the 3.5 upgrade, with all 4 modules off, and then activate them, one at a time, until CPU usage starts climbing? That would allow us to narrow things down a bit more.
Thanks!