Hi team
I’ve been facing this issue since a long time now. Whenever we start getting good traffic, the CPU usage spikes to 100% and the site is unreachable to users.
I’ve been tweaking it since months now with fail. It’s a nginx-varnish-php5-fpm-fastcgi-xcache setup with W3TC, page cache, object cache, database cache & browser cache on.
I read somewhere in the Newsmag forum that it might be due to the VC plugin. (My version is 4.11). I’m using New Relic to check what is causing the spike and it seems index.php is the culprit. I also fixed the header error at line 6 by using the if, else code. But I keep getting some error saying GET index.php timed out.
Is VC causing this issue? Should I disable VC on post pages? How to do that?
Sorry, forgot to add my server details.
16 core processor
48GB
480GB SSD
We had lots of issues with VC on our server with multi-XEONS, 32GB RAM, etc.
In our case – awhile back – was to use the beta ‘shim’ plugin which Radu (of TagDiv) came up with, which allowed us to use the most common blocks for story content to setup a fancy home page, where we’d use VC for short period to build/edit page, turn it off, and leave ‘shim’ plugin active.
This has evolved 2 years later into the TD Composer plugin, which does not replace/clone/ripoff VC, but takes that idea of the TD custom modules/blocks into their own plugin to build a nice homepage and strips out most of the more arcane stuff that “most” people don’t use.
So, that is worth a try.
Also ensure you disable loading of VC on posts if not actually using it for posts.
Hope that helped a little.
We’re now using the TD COmposer plugin and don’t have VC installed anyplace anymore.
You should also tr to update your version of the plugin if you still want to use it. You can use this guide: https://forum.tagdiv.com/how-to-update-visual-composer-plugin/
Thank you!
Hi Chris
Thank you for the help. I’m a bit worried about compatibility issues that might arise. It is a prod server.
Also, how to disable VC on individual posts?
Hi Bogdan
I have not updated the theme since we have made many changed in the theme post deployment. Hence would it be wise to update VC without updating the main theme? Will there be compatibility issues? It’s a prod environment and we can’t afford to risk it.
Hi,
We only recommend updating both as we have not tested newer versions of visual composer with older versions of the theme. If you do have issues with high cpu usage, then you should give it a shot and download the theme but i cannot assure it will work properly with older versions. You can create a testing site (a sub-domain copy of your main site) and test out the newer version of VC or the tagdiv composer on a sub domain so you will not affect the main site.
Thank you!
