Kinsta blacklisting WPP, a follow up

Hi, I fall in serious problem after updated your plugin. Now this plugins don’t support font. plz help me .

Hi @aamasum,

Please update to version 5.3.5 as soon as possible and let me know whether that fixes the issue.

Also, please post in the right place next time. This topic is completely unrelated to the issue you’re reporting.

I’m with Siteground (GoGeek shared hosting) and am using WPP together with Broken Link Checker, which are both potentially heavy plugins, but My CPU/account resource usage is way within limits and things are ticking over just fine. Both plugins have excellent documentation explaining how they work and how to use them according to available resources.

It is beyond me how a host can ban a plugin, on shared or VPS packages. As a client, you get your allotted resources, what you do with them should be up to you. Siteground do run a tight ship and will give you fair warning if/when you exceed resource usage and they will cut you off if you go too far, but, you also have a usage graph to monitor things in order to proactively fix problems before you reach limits, and even then, a few quick ‘red lines’ won’t be a problem, I find them very reasonable. In the meantime, you are free to run any plugin you like.

I’m with you there, @sean-h.

In regards to the Kinsta situation, I shared the documentation with their team so they could learn about the possibilities WPP offers to lessen its impact on performance.

They could have, for example, required customers to use Redis which Kinsta offers as a paid “add-on” for $100 USD a month per site (at the time of writing) to allow the usage of the plugin. Or, as other hosting providers, they could just cut off sites that are using more resources than they should like you said. Unfortunately, after 9 months of waiting this was the conclusion they drew.

Just to mention another example that had a different outcome, GoDaddy also banned the plugin some time ago and for the exact same reasons. Also upon users’ request, I reached out to their IT team and they were way more receptive and even provided code changes suggestions that ultimately led to the implementation of the Data Sampling feature which is why today you can use WordPress Popular Posts on GoDaddy’s servers. A win-win situation for everyone.

Anyways, this comment got way too long and I haven’t even had breakfast yet so I’ll stop here haha.

Thanks for commenting!

I’ve been thinking, as much as I try not to, because it hurts….both Siteground and Kinsta operate on Google Cloud Platform, who charges clients (the likes of SG and Kinsta) for resource usage. In other words, you pay GCP for every cpu second, etc, or something to that effect. This would suggest that Kinsta is being cheap by not allowing certain plugins that might use more resources than usual because GCP in turn bills them accordingly, and Kinsta charges way more than Siteground….way more…so considering Kinsta’s pricing, they should then be able to shoulder the odd client that uses a slightly heavier plugin.

It’s a bit like a restaurant that offers bottomless coffee for a fixed price but bans certain clients because they drink too much (coffee).

I was curious, so did some (more) research. To add insult to injury, Kinsta don’t actually do shared hosting, all their plans are dedicated. So why on this green earth do they limit what their customers do on their servers when it won’t affect anyone but that particular customer. The only possible reason I can think of is what I suggested in my post above.

• This reply was modified 3 years, 4 months ago by Sean.