100% CPU every couple days with LS Plugin enabled

  • Resolved imagophilos

    (@imagophilos)


    4 months, 2 weeks ago

    We are at the end of our (limited) knowledge. The hosting provider (Hosterion, Romania), a certified Litespeed server, is of no help. They actually recommended to switch to Rocket and not use LS anymore.

    We have LS plugin enabled, with only basic preset. Every couple days the site frontend locks down in 503 and CPU stays blocked at 90% – 100%.

    As soon as we either deactivate LS or switch on the “Disable all features” toggle, everything runs ok.

    If we click: “View site before optimization”, it runs ok.
    If we click: “View site before Cache”, it runs ok.

    Running only basic plugins plus LS gives the same result. It definitely has something to so with either the plugin, or the server or both, but we simply cannot identify it.

    Our REPORT Nr. is: QXUVAIUF

    We think we narrowed it down to the Image Optimization section. If we disable the plugin (or stop all optimizations) and reenable it without Image Optimization crons (Especially Pull Cron). It runs ok-ish. There are cache misses all over the place, even for pages where a user just bought the product, so that product page should have been cached. But we can live with that.

    Our main concern is the constant 503 episodes, and it drives us mad, and costs us customers.

    Please help.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support qtwrk

    (@qtwrk)

    based on your description , the 503 is most likely happened due to reached max PHP concurrent number , by default it’s 5 or 10 , by that saying , your site can only have 5 or 10 PHP processes concurrently , when image pulling , it fires multiple requests in parallel , which it may inadvertently hit the limit and further request will either be queued in line and wait for previous PHP process frees up , or wait to long ends up in 503

    let me check with our dev if there is any way to disable parallel pull or define the concurrency

    Plugin Support qtwrk

    (@qtwrk)

    as test, please try this

    edit file /wp-content/plugins/litespeed-cache/src/img-optm.cls.php at line 892 , you will see $imgs_per_req = 1 add a line before this line with content return 1;

    see how it goes when pulling images

    Thread Starter imagophilos

    (@imagophilos)

    Thank you so much for looking into this. I will try the adjustment and be back with an answer.

    Plugin Support qtwrk

    (@qtwrk)

    thanks, please let me know how it goes

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.