100% CPU when using Visual Composer after site migration

Posted in: Newspaper
Post count: 1

We’re experiencing 100% CPU load followed by a HTTP 503 error for a couple of minutes when doing either of the following operations:

– Saving a Visual Composer page

– Viewing “Backend editor” of a Visual Composer page

Disabling WordPress Heartbeat reduces the load a bit.

This worked fined before we migrated our site to a new web host.

We’ve removed all plugins, adding one after one to determine the culprit, and Visual composer seems to be the cause.
When contacting our web host we were told to contact the author of the plugin.

Any suggestions on how to proceed?

Thanks!

Post count: 20685

Hi,

We have not had any negative feedback regarding this. Please make sure that you use the latest version of the theme and the plugins bundled in the package.
The theme has these server requirements – https://forum.tagdiv.com/requirements-for-newspaper/ and requires modifications to be made to some parameters if needed – https://forum.tagdiv.com/system-status-parameters-guide/
It is recommended to use WP Super Cache – https://forum.tagdiv.com/cache-plugin-install-and-configure/ with the theme. There is also an available tutorial about improving website performance – https://forum.tagdiv.com/how-to-make-the-site-faster/
If you are saying that everything was fine before moving to the new host, maybe the problem is there since we have no complaints regarding this issue and everything is working as intended. Please let us know how it goes.

Thank you for understanding!

Post count: 45

.

Post count: 9544

We had major CPU issues on our old system with Visual Composer, and found the TD Composer solution the best fit for us (we were using old ‘shim’ solution originally). We’d get spikes going from .9 to 72 !~ …

Several things
a) make sure you have PHP 5.6 or higher. 5.4 and below are *dogs* and should no longer be used for WordPress. PERIOD.
b) doubly make sure you have at least 64M allocated to WP in both your host settings and in your wp-config.php file (we do 128M and above, but another story)
c) make sure you periodically optimize your DB with WP-Optimize of similar
d) limit queries “per page” — for example, no more than 5 “block items” per page

Might help.

Chris

Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic.