• Resolved speakoutenglish

    (@speakoutenglish)


    I noticed rather significant spikes in my CPU seconds recently. Looking back it turns out they started from a recent update of SGO.

    I disabled “File-Based Caching” and things have returned to normal.

    Iain

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

    (@ivandzh)

    Hello Iain,

    The file-based caching feature of the plugin includes several settings which may affect the overall amount of used CPU resources, depending on the content that is being processed. This includes all internal requests made by active plugins and templates.

    In case you want to keep the feature enabled, we would suggest to first try deactivating only its user-specific cache generation and content preheating options after which compare the results. If the website you are experiencing problems with is hosted on our servers, we also recommend getting in touch with our support staff by submitting a ticket through our ticketing system.

    Best regards,
    Ivan Dzhangozov

    Thread Starter speakoutenglish

    (@speakoutenglish)

    Thank you for your reply.

    I am hosted with SG.

    I have disabled this function and everything is fine.

    Your site shows a red line on CPU seconds. With this function on it doubles anytime I update pages almost immediately.

    I look forward to the next update.

    Plugin Support ivandzh

    (@ivandzh)

    Thank you for the update.

    We would recommend opening a ticket through your SiteGround account and provide us with the name of the affected website. This way we can perform further investigation of the issue in greater detail.

    Meanwhile, we remain available if you need further assistance regarding another website.

    Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    On SiteGround servers the File Based caching works alongside the Dynamic caching. This means that it will be triggered only if you enable it for logged in users. In addition to that, preheating could cause such spike because of the way this optimization works. You should check the access log for that site and the scripts executed to see what is causing it. As my colleagues said, contact our team and they will investigate further.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Spikes in CPU time with File-Based Caching’ is closed to new replies.