anonymized-11892634
(@anonymized-11892634)
@randomuser2000 this sounds like more of a hosting problem rather than an issue with the plugin.
-
This reply was modified 8 years, 11 months ago by
anonymized-11892634.
That does indeed sound more like a hosting issue, but some of it can be avoided, even on cheap shared hosting. “Cheap” is intended to distinguish from quality shared hosts, which do exist. Anyway…
It’s very probable that your webhost has throttled your site for excessive CPU usage, and slow MySQL queries:
1. Image optimization IS CPU intensive. There is no way to compress images and use zero CPU… If you are uploading 65MB of images with EWWW’s compression on, it WILL hit the CPU on your server hard, and many webhosts will throttle your site for that.
Solution? Use the API, that’s what it was created for.
2. When you turn on PNG to JPG, you want image urls updated, right? Well, on a large site, that can be an expensive query to run, and again you might run into throttling issues. If a shared host has overcommitted their resources they cannot permit you to run very many expensive queries. Their quick and dirty solution is to throttle anyone who runs too many queries that they consider “too expensive”.
Solution: stop being so cheap and upgrade your hosting. If your site is big enough to cause expensive queries that your webhost doesn’t like, its time to move on… That’s a little dramatic, but hopefully you get the point.
It could be inded a hosting issue but first let’s clarify some points:
I am not running my site on cheap hosting. I run it on a VPS which uses Nginx, MySQL and PHP-7.0-FPM. There is also different servers that I use for mails, downloads etc. And CDN of course. On top of that caching systems like WP-Rocket, OPcache, Redis are all present.
Also total size of the images were 65 MB. Not every single of them was 65 MB. Some of them were 230 KB, some them were 2 MB etc…
Normally the plugin is very good I think. It is even for free.
But this problem really kills it for me. Again it could be some misconfiguration on the server side. Is there any extra configuration options you can suggest for PHP, Nginx or MySQL to rectify this situation I am ready to try them.
Just happened to check this, can you contact me here with your debug information and I’ll see if I can spot anything else that would have contributed to the problem: https://ewww.io/contact-us/
I was looking through my own nginx configs today, and came across the two settings I think will help:
1. In nginx.conf, increase worker_processes to 8
2. In your php-fpm config, should be something like /etc/php/7.0/fpm/pool.d/www.conf increase the pm.max_children setting to 250.
Even on minimal hardware, nginx + php-fpm can handle way more connections than the default configs permit.
