CPU Usage

Same problem here! My web is in SiteGround. The configuration was ok, I even asked Siteground experts to configure the plugin for me. After many tries, the problem is still there and my web was limited several times because of MailPoet.

Hmmm, I’m on Siteground too. I wonder if something in the last update upset something?

I’ve had to deactivate the plugin for now. I use the signup in several places so it’s not a click!

My CPU has gone from 12000 to 2500 since deactivating.

Hi,

SiteGround and Amazon EC2 will disable your site if you use the MailPoet’s task scheduler because these hosts will dislike its long CPU cycles, unfortunately.

If your website is hosted on SiteGround or in an Amazon EC2 instance, please use the “Visitors to your website” option.

As per my original post, the option is (and always has been!) set to “Visitors to your website”. And as I said, I even tried setting it to the MP task scheduler and back to “Visitors”, but this made no difference.

So that’s not it – unless the option isn’t working in the latest version of the plugin?

It’s the same for me. The configuration was okay. I repeat: ‘I even asked Siteground experts to configure the plugin for me’.

That was not the problem.

This is still an issue. I am seeing a direct correlation between the Mailpoet plugin and CPU usage. To be more plain, when I see CPU usage spiralling up on my hosting, deactivating the plugin reduces that immediately and significantly from over 3000 (in their figures) to a few hundred.

I’m wondering if the plugin cannot differentiae robot traffic, and therefore is hooking into visits that aren’t real humans?

However, I should add that spikes seem to relate to updates every time. And yes, I am clicking the ‘visitors’ option off and on every time it updates to makes sure it’s set correctly.

I installed Mailpoet 3 a couple of months ago, yesterday after I made a backup with Updraftplus, my CPU usage jumped to 100x the usual usage. I consumed in 18 hours what is allowed for one week. I am on a shared Growbig plan on Siteground. After some tests, I realized Mailpoet is causing this issue, and I was on the “visitors” option as well.
I tryed to change it to Mailpoet script and back to “visitors” but I had to disable the plugin again, it’s not working.
Did you discover anything new about that? My plan was to buy the plugin when I reach 2000 visitors, I am not too far from there, but now I think I will have to find a different soluzion, unless I can fix this problem.

No response from the developers here. Though you should be able to get support to respond, I would say there’s no guarantee that the ‘pro’ version will not have the same issue.

Thanks for your answer. Did you try Mailster? It seems to be a similar WordPress application, it’s even cheaper than Mailpoet.

I have had multiple sites with HUGE jumps in CPU usage due to this plugin update to version 3. I have DELETED the plugin on all sites until the issue is resolved by the developer. The response from the developer does not resolve the issue with anyone utilizing SiteGround. Please respond with a fix as multiple sites are waiting. Thank you.

not sure what is going on with the MailPoet team, their support, and what was once timely and effective response (i’m specifically referring to a “Please be careful with your statements” read on a previous post, which sent shivers along my spine), but i have to join this quite long list of unhappy SiteGround users experiencing problems with the “Visitors to your website” option.

the site uses MailPoet

here’s a log posted by SiteGround assistance which hopefully can be of help to the MailPoet team. in any case, it shows that we are not making anything up, the MailPoet plugin has definitely something not working properly under specific conditions (namely SiteGround accounts – type: GrowBig), which does not depend on the “proprietary cron script”, but on the default and suggested “Visitors to your website”:

outer&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjgwYjA1In0″ “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:01:36 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6Ijk4ZTBkIn0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6Ijk4ZTBkIn0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:01:56 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjFlNGU3In0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjFlNGU3In0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:02:15 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjE4MWEwIn0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjE4MWEwIn0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:02:34 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6ImRlODQyIn0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6ImRlODQyIn0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:02:54 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6Ijk1YjVmIn0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6Ijk1YjVmIn0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:03:13 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6ImE3MGE5In0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6ImE3MGE5In0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:03:32 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6Ijk1MDcxIn0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6Ijk1MDcxIn0” “MailPoet Cron”
185.197.128.178 – – [28/Mar/2018:14:03:52 +0200] “GET /?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjliNDliIn0 HTTP/1.0” 200 – “https://@@@@@@.@@@/?mailpoet_router&endpoint=cron_daemon&action=run&data=eyJ0b2tlbiI6IjliNDliIn0” “MailPoet Cron”

for the time being, MailPoet plugin has to stay disabled (we’ve had the site turned off 3 times in 48 hours). if the MailPoet team is able to acknowledge and fix it in proper time, then it’ll remain our newsletter plugin of choice. otherwise it’s time for us to look elsewhere, i suppose.

UPDATE: just seen a new release with this in changelog:

Fixed: scheduled newsletter task no longer runs non-stop when “site visitor” option is enabled. Thanks to @amedic, @conorsboyd and @aspasa for reporting the issue on the forum!

hopefully this sorts the issue.

Thanks. I saw that too! ?? So there WAS an issue with the plugin that (once again) has not been acknowledged here by the developers, while discussions go on about using other plugins for the job.

Way to go winning users over to buy the pro version. Not.

It seemed they solved the issue really fast, with a new release. From now on, when I update Mailpoet I will check CPU time usage on my website, to check there is not a similar problem.
Any opinions about Mailster? I like Mailpoet but I will consider that alternative, if Mailpoet causes problems again