Script maxes out CPU server resources

  • Hi, I love your plugin, and it sped up my page loads considerably. I’ve had it installed about a week, and just got a warning from my host Siteground that my site had reached its monthly allowed CPU seconds of allowed usage of 800000 CPU seconds per account.

    My site has always been well under the CPU usage maxima, so I checked the CPU usage report that lists the number of executions from the beginning of the current month, and /home/mysite/public_html/wp-content/plugins/wp-youtube-lyte/lyteThumbs.php was the largest consumer by far, with 870,317 executions. Not sure what was going on, but I unfortunately had to uninstall the plugin for now. Thought I would just let you know! Thanks for all your hard work on this.

    • This topic was modified 6 years, 1 month ago by itruemper.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    Unticking the “cache thumbnails locally” option should (could have) fix(ed) that.

    I don’t know your site or the number of videos or the number of visitors; does it make sense that the youtube thumbnails get requested that often?

    frank

    Thread Starter itruemper

    (@itruemper)

    Thanks for the fast reply and suggestion. The site gets 150K pageviews monthly mostly to my lists of recommended TV series with up to 40 videos on a post (here is an example: https://www.secondhalftravels.com/spanish-language-tv-shows-netflix/), so it makes sense it could max out.

    I’ll try again next month with caching off when my limits have reset. Thank you!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    OK, feel free to keep me posted ??

    Thread Starter itruemper

    (@itruemper)

    Will do, thanks again! =)

    Thread Starter itruemper

    (@itruemper)

    Hi, Frank, quick update. I reinstalled the plugin March 1 with the “cache thumbnails locally” option turned off. In the last week /home/mysite/public_html/wp-content/plugins/wp-youtube-lyte/lyteThumbs.php consumed 550 CPU seconds… much better than 870K, obviously! Worth noting perhaps that it’s the only plugin that appears in the top 10 list of executed scripts in the CPU usage report… all the others are WP core files.

    Not a big deal right now as the CPU seconds are well below max again. Thanks again for your help and for this great plugin.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    great to read, but

    In the last week /home/mysite/public_html/wp-content/plugins/wp-youtube-lyte/lyteThumbs.php consumed 550 CPU seconds…

    is still pretty weird, as when thumbnails are not cached locally, lyteThumbs.php is not (supposed to be) used? Maybe check if there are files in wp-content/cache/lyte and/ or check your access logs for who accessed lyteThumbs.php?

    Thread Starter itruemper

    (@itruemper)

    Good thought… there were hundreds of image files in the cache dating from early last month. I’ve cleared them out now. I’ll continue to monitor the CPU usage to make sure the issue is resolved. Thanks!

    @itruemper I got the same issue.
    I’m on Siteground, and lyteThumbs.php is on the top of the list.

    Please inform if disable caching solve the problem?

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    given she wrote

    I reinstalled the plugin March 1 with the “cache thumbnails locally” option turned off. In the last week /home/mysite/public_html/wp-content/plugins/wp-youtube-lyte/lyteThumbs.php consumed 550 CPU seconds… much better than 870K, obviously!

    is seems it did. it looks as lyteThumbs.php was bombarded with requests, maybe even for YouTube video’s that weren’t in cache yet, which would have the script fetch each image from YT. I’ll think about some sort of extra checks to avoid such issues in the future.

    Thread Starter itruemper

    (@itruemper)

    Thanks, Frank. Yep, disabling caching fixed it, and I also had to clear out the cache.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Script maxes out CPU server resources’ is closed to new replies.