unusal amount of compute cycles, again

  • Resolved robertburr

    (@robertburr)


    5 years, 6 months ago

    Suddenly, once again as before, my sites with mailpoet are seeing an unusually high amount of compute cycles. There is no a lot of activity that would explain this. This was fixed in the past, it’s now back again.

    Support at Liquid Web tells me: “there were quite a few calls to wp-cron.php from the site itself, except instead of calling it locally, it went outside to the internet and the site called itself. Having your site call itself that way will cause it to consume more resources, so doing a relative url call would be best.”

    Any insight as to a way to get back to normal is appreciated.

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

  • @robertburr
    How many sites do you have Mailpoet installed and active on?

    Thread Starter robertburr

    (@robertburr)

    Four

    @robertburr

    Where are those sites hosted on Managed WordPress, Cloudsites, Cloud VPS or something else?

    Thread Starter robertburr

    (@robertburr)

    hosted at Liquid Web cloud sites. thanks for your help.

    @robertburr

    I would check with Liquid Web support if a server-side cron is possible to setup on Cloud Sites.
    https://kb.mailpoet.com/article/129-what-is-the-newsletter-task-scheduler

    Thread Starter robertburr

    (@robertburr)

    some info from the liquid web support staff.

    I found that this site has over 19,000 ‘POST’ requests to the /wp-cron.php file from 05/29/19 – 05/31/19. Anything that has to do with scheduling posts or publications and really anything date/time oriented is governed by the wp-cron.php file. These scheduled tasks will consume CC’s(Compute Cycles), which leads me to believe either your sites theme or plugins are the issue.

    6317 POST /wp-cron.php (# of POST made on 05/29/19)
    5942 POST /wp-cron.php (# of POST made on 05/30/19)
    6596 POST /wp-cron.php (# of POST made on 05/31/19)

    Below is the number (#) of times an IP address made a POST request to /wp-cron.php”

    501 207.246.249.194 “POST /wp-cron.php
    464 207.246.249.206 “POST /wp-cron.php
    462 207.246.249.204 “POST /wp-cron.php
    449 207.246.249.196 “POST /wp-cron.php
    435 207.246.249.199 “POST /wp-cron.php
    427 207.246.249.203 “POST /wp-cron.php
    425 207.246.249.202 “POST /wp-cron.php
    420 207.246.249.193 “POST /wp-cron.php
    409 207.246.249.201 “POST /wp-cron.php
    405 207.246.249.198 “POST /wp-cron.php
    395 207.246.249.197 “POST /wp-cron.php
    387 207.246.249.200 “POST /wp-cron.php
    383 209.196.218.13 “GET /feed/p2.ajax/
    382 207.246.249.195 “POST /wp-cron.php
    381 207.246.249.205 “POST /wp-cron.php

    You can see that the 207.246.*.* IP[range] addresses are our servers’ outbound IP’s, this indicates that plugins are making outbound calls to complete their tasks/requests. So while your traffic isn’t high enough to cause this issues scheduled tasks are consuming more PHP/resources to complete tasks.

    Hi @robertburr,

    Out of the box, MailPoet doesn’t use wp-cron.php at all. Instead it uses our own task scheduler or it’s possible to set up a custom server-side cron as @lukefiretoss pointed out.

    If you can get us the full request/access log for the requests we’ll be able to see exactly what is causing the issue.

    Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘unusal amount of compute cycles, again’ is closed to new replies.