[wp-hackers] Multi-sites in WP 3.0 running SLOOOOOOOOW
jpotkanski at tribune.com
Fri Sep 17 19:01:02 UTC 2010
Don't forget op caching for PHP itself: xCache or APC. That's a 25% to 200% performance increase.
From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Jeremy Clarke
Sent: Friday, September 17, 2010 1:58 PM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Multi-sites in WP 3.0 running SLOOOOOOOOW
On Fri, Sep 17, 2010 at 1:15 PM, Gregg F. Tomlinson <gregg at fatheaddesign.com
> These are hosted on a private server (physical, not cloud-based) at
> Rackspace so I know it's not server load or traffic related, it's got to be
> the code itself.
You shouldn't take this premise for granted, or at least you need to account
for server configuration seperately from laod/traffic.
My experience with dedicated servers has taught me that their default
configurations are often FAR WORSE than a shared hosting configuration. When
preparing shared servers hosts will do everything possible to make the
server run well for all possiblities, ultimately creating a super-compatible
environment where things like WP just work. The tradeoff is that all the
compatibility overhead slows down the whole thing to a significant degree.
Dedicated servers on the other hand are often given to you fresh, with the
default linux configurations. In this case both MySQL and Apache not only
need to be tuned for your particular use, but the default values might be
downright garbage of your server setup. On a MySQL server I set up with many
gigabytes of RAM the default settings were only configured to use 512MB
worth of it, making all the other RAM a waste until I changed the
configuration to take advantage of it.
You should look into the queries being run and the load that your mysql
processes are taking up. Do you have mysql cache turned on? It makes a huge
difference if you aren't running something like memcached (though maybe you
should just jump right to memcached).
In terms of your problem being only the deeper pages that is strange. Could
it be a plugin that is only running on those pages? Did you try disabling
Too bad WP-Tuner is broken, that tool was awesome for this kind of thing.
Someone needs to resurrect it.
Code and Design | globalvoicesonline.org
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers