• we has 261,000 posts,
    Running 2 Dedicated Server, Webserver / Mysql server.
    125000 unique visitor daily.

    my problem is “after a new post is made, then the mysql used all cpu resource”. I have w3 cache.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator t-p

    (@t-p)

    – Please check the error logs on your server for a more specific error message and see why it’s failing. If you need help locating them, ask your hosting provider to help you with that.
    – If you cannot find error logs or if you don’t find any helpful info in the error logs, try Enabling debugging and post the results.

    Thread Starter ravsiyan

    (@ravsiyan)

    i think after a new post is made, cache is cleaned.

    `
    Notice: add_option was called with an argument that is deprecated since version 2.3 with no alternative available. in /home/jetski2/public_html/wp-includes/functions.php on line 3739

    Strict Standards: Declaration of Walker_Category2::start_lvl() should be compatible with Walker::start_lvl(&$output, $depth = 0, $args = Array) in /home/jetski2/public_html/wp-content/themes/wptheme/includes/fn-general.php on line 254

    Strict Standards: Declaration of Walker_Category2::end_lvl() should be compatible with Walker::end_lvl(&$output, $depth = 0, $args = Array) in /home/jetski2/public_html/wp-content/themes/wptheme/includes/fn-general.php on line 254

    Strict Standards: Declaration of Walker_Category2::start_el() should be compatible with Walker::start_el(&$output, $object, $depth = 0, $args = Array, $current_object_id = 0) in /home/jetski2/public_html/wp-content/themes/wptheme/includes/fn-general.php on line 254

    Strict Standards: Declaration of Walker_Category2::end_el() should be compatible with Walker::end_el(&$output, $object, $depth = 0, $args = Array) in /home/jetski2/public_html/wp-content/themes/wptheme/includes/fn-general.php on line 254

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “Sidebar” sidebar. Defaulting to “sidebar-1”. Manually set the id to “sidebar-1” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/jetski2/public_html/wp-includes/functions.php on line 3792

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “Post Widget” sidebar. Defaulting to “sidebar-2”. Manually set the id to “sidebar-2” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/jetski2/public_html/wp-includes/functions.php on line 3792

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “single sidebar” sidebar. Defaulting to “sidebar-3”. Manually set the id to “sidebar-3” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/jetski2/public_html/wp-includes/functions.php on line 3792

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “single sidebar160” sidebar. Defaulting to “sidebar-4”. Manually set the id to “sidebar-4” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/jetski2/public_html/wp-includes/functions.php on line 3792

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “menu” sidebar. Defaulting to “sidebar-5”. Manually set the id to “sidebar-5” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/jetski2/public_html/wp-includes/functions.php on line 3792

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “Footer Widget” sidebar. Defaulting to “sidebar-6”. Manually set the id to “sidebar-6” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in /home/jetski2/public_html/wp-includes/functions.php on line 3792

    Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

    __construct()

    instead. in /home/jetski2/public_html/wp-includes/functions.php on line 3624

    Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

    __construct()

    instead. in /home/jetski2/public_html/wp-includes/functions.php on line 3624

    Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

    __construct()

    instead. in /home/jetski2/public_html/wp-includes/functions.php on line 3624

    Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

    __construct()

    instead. in /home/jetski2/public_html/wp-includes/functions.php on line 3624
    Notice: Undefined variable: output in /home/jetski2/public_html/wp-content/plugins/facebook-and-digg-thumbnail-generator/facebook-and-digg-thumbnail-generator.php on line 268
    xmlns:og=”http://ogp.me/ns#” xmlns:fb=”http://ogp.me/ns/fb#”>
    Notice: Undefined offset: 0 in /home/jetski2/public_html/wp-content/plugins/only-tweet-like-share-and-google-1/tweet-like-plusone.php on line 229

    Moderator t-p

    (@t-p)

    Have you tried:
    – deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
    – If you can’t get into your admin dashboard, try resetting the plugins folder by FTP. Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder (if you have created such folder). The easiest way is to rename that folder to mu-plugins-old.

    Thread Starter ravsiyan

    (@ravsiyan)

    thanks

    but

    everything was fine, after a new post is made, then all of a sudden, hundreds of mysql processes were running :

    [18:31:06] root@ski-jet [~]# mysqladmin proc
    +——+——————+——————————+——————-+———+——+———————-+——————————————————————————————————+
    | Id | User | Host | db | Command | Time | State | Info |
    +——+——————+——————————+——————-+———+——+———————-+——————————————————————————————————+
    | 1 | wp_press | webpage22.fadns.com:46062 | wpski_wp | Query | 37 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts |
    | 3 | wp_press | webpage22.fadns.com:46075 | wpski_wp | Query | 38 | Sending data | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = ‘post’ AN |
    | 14 | wp_press | webpage22.fadns.com:46084 | wpski_wp | Query | 37 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts |
    | 16 | wp_press | webpage22.fadns.com:46087 | wpski_wp | Query | 36 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts |
    | 20 | wp_press | webpage22.fadns.com:46091 | wpski_wp | Query | 37 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts |
    | 22 | wp_press | webpage22.fadns.com:46098 | wpski_wp | Query | 5 | Sending data | SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (480560) ORDER BY meta_id ASC |
    | 24 | wp_press | webpage22.fadns.com:46100 | wpski_wp | Query | 37 | Copying to tmp table | SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts |

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Database problem’ is closed to new replies.