WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 8 months ago

Last modified 8 months ago

#19995 closed defect (bug) (invalid)

Slow down of access to Multi-Site Admin area when Upgrading to 3.3.1

Reported by: bastosmichael Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.3.1
Component: Multisite Keywords:
Focuses: Cc:

Description

I've done a search and didn't see a trouble ticket for this so I wanted to post it and see what the feedback looked like. With the upgrade to WordPress 3.3.1 I've seen a very big slow down of access to the Admin area for both the Network sites as well as the Network Admin. I thought it was my server lagging at first or maybe an issue with me having to clean up my MySQL server but I've heard from others whom I know that also run Multi-Site installs having the same problem as well. One gentlemen's client thought his site had even been hacked because of the amount of time it was taking to get to the admin area but after running the necessary security tools it was realized that the server was secure but the lag did exhist. Any thoughts?

Change History (6)

comment:1 nacin2 years ago

Without any data or proof, or knowledge of the server environment, there's nothing we can do here.

comment:2 bastosmichael2 years ago

My apologies, here are the specs for the gentlemen I mentioned, not sure if this helps, If this isn't enough data to go off of then just close the ticket and I'll try to get more data before I resubmit down the road.

Here are the server spec's:

php53-5.3.3-1.el5_7.3
mysql-server-5.0.77-4.el5_6.6
httpd-2.2.3-53.el5.centos.3
kernel 2.6.18-274.12.1.el5

CentOS 5.7 updated

free
total used free shared buffers cached
Mem: 8167324 6278348 1888976 0 248360 5164152
-/+ buffers/cache: 865836 7301488
Swap: 6144828 0 6144828

ps aux | grep apache

apache 6642 7.0 0.3 239824 30896 ? S 02:18 0:00 /usr/sbin/httpd
apache 6643 5.7 0.3 235724 27896 ? S 02:18 0:00 /usr/sbin/httpd
apache 6644 0.0 0.0 215164 5224 ? S 02:18 0:00 /usr/sbin/httpd
apache 6645 0.0 0.0 215164 5224 ? S 02:18 0:00 /usr/sbin/httpd
apache 6646 0.0 0.0 215164 5224 ? S 02:18 0:00 /usr/sbin/httpd
apache 6647 0.0 0.0 215164 5224 ? S 02:18 0:00 /usr/sbin/httpd
apache 6648 0.0 0.0 215164 5224 ? S 02:18 0:00 /usr/sbin/httpd
apache 6649 0.0 0.0 215164 5224 ? S 02:18 0:00 /usr/sbin/httpd
Last edited 8 months ago by SergeyBiryukov (previous) (diff)

comment:4 follow-up: weschyrchel2 years ago

Nacin, Michael was posting for me.

The url is http://www.controltec.biz. Even going to http://www.controltec.biz/wp-admin , you can experience the slowness.

Since the update to Wordpress 3.3.1 the web site administrative backend takes up to 2 minute to move between pages. The frontend is fine. The issue is a common issue now with the multi-site feature. The issue is not RAM, CPU or anything with the server. I have optimized memory for Wordpress and PHP. I have disabled all plugins, etc. Nothing...

We also ran the WP Optimize plugin. No improvement.

In addition we implemented the following suggestion.

If the issue is your queries are taking too long then in your wp-config.php file, add this line of code to the top:

define('SAVEQUERIES', true);

Then, in the theme's footer.php file, you can do this to dump all the queries and how long they took:

if (SAVEQUERIES) {
global $wpdb;
echo '<!--\n';
print_r($wpdb->queries);
echo '\n--!>';
}

Then looking at the source of the page will show all the queries and a number showing how long they took.

After you do this, turn the SAVEQUERIES back off by setting it to false in the wp-config.php file. You don't want it to spit out the queries all the time.

If it's a wp-cron problem (possible), then you can possibly manually clear it up quickly by doing the following:

Remove or comment out this line from wp-cron.php:

if ( $_GET['check'] != wp_hash('187425') )
exit;

Try these first but there may be other things you can try if that doesn't work.

ALSO, the latest we are trying is this, http://wpengineer.com/1176/analyze-wordpress-performance-plugin/

If you have any suggestions, we would appreciate the help. Thank you!

Last edited 8 months ago by SergeyBiryukov (previous) (diff)

comment:5 in reply to: ↑ 4 SergeyBiryukov2 years ago

Replying to weschyrchel:

Then looking at the source of the page will show all the queries and a number showing how long they took.

Were you able to spot any slow queries as a result of this?

comment:6 jeremyfelt8 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Site specific issue on 3.3.1, no additional details from the original reporter.

Note: See TracTickets for help on using tickets.