Navigation
This is archived content. Visit our new forum.

Tagged: 

  • Author
    Posts
  • #1047499
    RBradyFrost
    Participant

    My site is: rbradyfrost.com
    WordPress version: 4.5.2
    X version: 4.5.2
    Cornerstone version: 1.2.4

    Frequently, but not always, Cornerstone takes a long time to save. This sometimes results in the database connection crashing and I am not able to access my site for a few minutes. I contacted my host and they said that my account has been throttled for cpu utilization at times that seem to coincide with these occurrences. Their logs show several action=cs_render_element log entries from my ip to /wp-admin/admin-ajax.php? — In one such instance, the log reports: “CPU Usage: 104.6% (warning)Snapshot”

    I have the logs provided by the host if they will help and I can attach them privately.

    #1047500
    RBradyFrost
    Participant
    This reply has been marked as private.
    #1047560
    RBradyFrost
    Participant

    I have added:
    define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
    define( ‘WP_MAX_MEMORY_LIMIT’, ‘512M’ );
    to my wp-config.php file and still experience the long delay in attempting to save my current draft blog post.

    #1047835
    Rad
    Moderator

    Hi there,

    Thanks for writing in.

    According to the logs, your account type is Shared. Shared hosting’s allocated resources are too limited, hence, reaching load limit is easier to achieve.

    For example, if the allocated cores are 2, and the process used up the 2 cores then it will be 100% load. But what if there are 4 cores and used up 2 cores, then it will be just 50% load. We can’t just say it’s because of the script process why it’s loading 100%. Allocation is has a role too.

    And with shared hosting, memory limit/allocation isn’t usually allowed. Your added code will not work unless your hosting allows it.

    Shared hosting isn’t recommended on the site that has rich features. It’s the same as you can’t run modern software on old systems.

    And according to the logs, ajax requests has 5 counts, end points has 5 to 20 counts which are pretty small to reach the limit. A page with long content can have 100 render requests and can still work.

    Thanks!

  • <script> jQuery(function($){ $("#no-reply-1047499 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>