• Resolved chrisalton11

    (@chrisalton11)


    SiteOrigin has recently started causing major CPU Usage issues every time we try to update the website. I know that previous versions of the pages in page-builder are auto-saved so that they can be restored if necessary.

    Is it possible that these auto-saves are piling up and causing the site to overload and lag? If not, do you have any other suggestions about what might be causing this?

    Thanks again for your time,

    Chris

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Andrew Misplon

    (@misplon)

    Hi Chris

    Thanks for posting. Is the issue occurring on all Page Builder pages?

    Thread Starter chrisalton11

    (@chrisalton11)

    Hi Andrew,

    Yes, it appears to be happening on every page. We use Site Origin with Classic Builder for editing the entire website, and even as a widget inside the Gutenberg Blocks footer.

    Any advice would be appreciated,

    Chris

    Plugin Support Andrew Misplon

    (@misplon)

    Hi Chris

    Thanks for the update. Lots of directions to take in an investigation like this one.

    • At Tools > Site Health you can check to see if WP is flagging server response time.
    • When the issue occurs in the admin you can try checking for errors in the console. Errors will be in red text https://www.ads-software.com/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis.
    • Try checking for a working baseline. Temporarily deactivate all plugins except for Page Builder and the Classic Editor. If you want to put the site into maintenance mode you can leave the maintenance mode plugin activated. With the above two or three plugins activated, does the issue persist?
    Thread Starter chrisalton11

    (@chrisalton11)

    Hi Andrew,

    I’ve hired someone to try to help me fix this SiteOrigin CPU issue but we still haven’t solved it. The Wordfence activity summary is showing Site Origin files being modified while no one is working on the website. Could you look at the screenshot in this Pasteboard link and let me know if it tells you anything about what’s happening?

    https://pasteboard.co/ICFBykW8P6FZ.jpg

    Thanks for your time,

    Chris

    Plugin Contributor alexgso

    (@alexgso)

    Hi,

    Can you please elaborate on what you’re seeing that suggests you’re experiencing major CPU usage? Are you seeing an alert or a notice? If so, can you please provide me with what you’re seeing? These alerts/notices can sometimes provide more insight into what’s going on.

    Do you get the same performance results if you temporarily disable all non-SiteOrigin plugins and switch to a default theme? Page Builder allows you to add non-SiteOrigin widgets and shortcodes and if something isn’t performing well it can sometimes appear as though Page Builder isn’t, but it’s actually just something being added with Page Builder. This test will allow you to confirm if it’s specifically Page Builder, or something else being added using Page Builder.

    If it performs better, try re-enabling each plugin you deactivated one by one until this issue returns. If it doesn’t, try reactivating your original theme.

    Is it possible that these auto-saves are piling up and causing the site to overload and lag?

    This is unlikely and would be indicative of other issues related to the server itself. Regardless, Page Builder uses the standard WordPress auto-saving and revision system so any plugin that allows you to manage those will also cover Page Builder. This article covers a few options you could use to manage your revisions.


    Could you look at the screenshot in this Pasteboard link and let me know if it tells you anything about what’s happening?


    The contents of your screenshot are expected. Your page contains widgets that require CSS to be generated and served to the user. Rather than generating this each and every page load we generate it once by caching the generated CSS and then serve that CSS each subsequent visit. This improves performance overall and it won’t directly impact performance when saving the page as it happens when a user views the page, not when the page is saved.

    Kind regards,
    Alex

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘SiteOrigin causing major CPU Usage issues’ is closed to new replies.