Kinsta hosting issues?

  • Resolved ryanbarthel

    (@ryanbarthel)


    8 years, 2 months ago

    Hi, I have a question about performance on a certain host provider. I use this plugin on WPEngine just fine, no issues. I’m building a site on Kinsta hosting and I’m getting Connection Timeouts. I contacted their support and they show that SOEFramework is making the WP-Cron run a lot which is maxing out the PHP-workers…. This is all over my head lol, but I’m wondering if I need to check my settings in SEO?

    I noticed that the “Enable Object Cache” checkbox shows up in WPEngine, but it’s not there in Kinsta. I have everything normal as the plugin was installed.

    – Enable Search, Enable Archive checked (in the database)
    – Transient Cache settings all unchecked

    Do I need to adjust my settings differently for Kinsta hosting? PS – they couldn’t help me because they said it’s a third party plugin that they don’t do support on.

    Thank you.
    – Ryan

Viewing 7 replies - 1 through 7 (of 7 total)
  • Pierre LeBaux

    (@lebaux)

    8 years, 2 months ago

    Hi, Kinsta is in my opinion relatively high end hosting. Please wait for plugin author @cybr to give you a statement. Thanks for patience!

    Thread Starter ryanbarthel

    (@ryanbarthel)

    8 years, 2 months ago

    No worries Pierre! Thank you for the quick response. Kinsta has a $30/m plan so it’s more affordable. I think the lowest plan used to be $100/m.

    Plugin Author Sybre Waaijer

    (@cybr)

    8 years, 2 months ago

    Hi @ryanbarthel,

    Thanks for reaching out!

    Non-technical:
    Preamble: This is the first time I’ve heard of this.

    There’s little I can suggest or inform with the ambiguity of the information provided.
    I’d like to ask you to ask them for more information on their findings, they’re free to contact me at any time on my contact page as well.

    Technical:
    Assumption: With opcode caching, which I expect Kinsta to utilize, it’s impossible to find the culprit. There might be a PHP notice or warning, but that shouldn’t directly correlate to performance issues.

    TSF only adds listeners for cache clearing, for when a post-state has been changed on WP_CRON. A state change includes a post deletion or a timed post-publication.
    These listeners carry no notable weight on the server by their very nature.

    TSF does not initiate cron runs, this is the server’s and WordPress’ doing.

    As for the object caching option: It is only visible when a custom object caching module is found. WP Engine has such a module, which explains why it’s visible there.
    Object caching in WordPress is intended to help with database offloading and to prevent database timeouts, which can happen if you suddenly get a spike in visitors. It doesn’t necessarily improve performance otherwise.

    Thread Starter ryanbarthel

    (@ryanbarthel)

    8 years, 2 months ago

    No worries, I was wondering if this is the first time you’ve heard of this haha. Is there a way I can send you screenshots of what they sent me?

    I guess from your perspective, what are the optimal settings I should choose in the performance tab?

    Kinsta wasn’t very much help, they said I had to get a hold of you since you’re the plugin owner… :/

    Thanks for the quick responses!

    Pierre LeBaux

    (@lebaux)

    8 years, 2 months ago

    Hi @ryanbarthel, hope you are having a nice weekend, apart from this issue 🙂 Please send your sceenshots via contact form and don’t forget to mention this support topic.

    Absolute best thing would be Kinsta techs directly contacting us, so we can iron out any issues without dragging you as a user into it. From historical standpoint, @cybr managed to fix all and any issues with other plugins/themes/hosting, if there was a will from other side. 🙂

    Again, sorry for the issues and your patience and thank you very much for standing ground with TSF! We appreciate that and we will try to get this resolved.

    Thread Starter ryanbarthel

    (@ryanbarthel)

    8 years, 2 months ago

    ok cool, i submitted it on your contact page. thanks!

    Plugin Author Sybre Waaijer

    (@cybr)

    8 years, 2 months ago

    Hi @ryanbarthel,

    Thank you so much for forwarding the messages.

    I asked you to ask them because many hosts tell me to become a customer prior engaging contact… it’s a vicious circle. 🙁

    TL;DR: Try disabling TSf to see if anything changes. It’s the only way to know if it’s the culprit.

    Background information:
    The assimilated data shows that TSF is the offender because TSF acts like an umbrella.
    This means that TSF loads itself into many hooks, and covers many points in WordPress’ execution. This includes the startup of WordPress’ plugins and the shutdown of PHP. Those are at the near start and definite end of a WordPress request, covering almost all of PHP’s execution time.

    So, if a request takes X seconds to complete, then TSF will show near X seconds of execution time, even if it only contributed to 1% of that time.
    It’s in fact dormant most of the time, waiting for the next action.

    To correctly obtain information on execution times, you’ll need to dissect every single PHP function call. Only then you know what’s truly happening, and this is difficult and very time-consuming.
    Advanced tools like xDebug help in that; it is what I’ve used to eliminate all known performance issues with TSF. However, tools like that aren’t meant to be used on live hosting, and tools like that won’t work with any form of opcode caching.

    To be certain, you could try turning off TSF to see if the timeouts stop.
    If they do, I’ll definitely investigate the cause, but it’s likely a plugin conflict.
    However, if they don’t, there’s definitely another offender.

    In the meantime, I recommend asking Kinsta if opcode caching is enabled. And if so, ask if it was enabled during the load assessment. If this is true, then the plugin execution time data is unfortunately useless.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Kinsta hosting issues?’ is closed to new replies.