hi,

this looks like a wordpress code/mysql issue to me:

jus...@justinlappy:~$ time wget http://sleepypenguin.homelinux.org/blog/
--2010-06-30 14:54:39--  http://sleepypenguin.homelinux.org/blog/
--- snip ---
2010-06-30 14:54:51 (2.35 KB/s) - `index.html' saved [25659]
real    0m11.861s
user    0m0.000s
sys     0m0.020s

jus...@justinlappy:~$ time wget
http://sleepypenguin.homelinux.org/blog/wp-content/themes/suffusion/style.css
--2010-06-30 14:59:06--
http://sleepypenguin.homelinux.org/blog/wp-content/themes/suffusion/style.css
--- snip ---
2010-06-30 14:59:08 (31.2 KB/s) - `style.css' saved [63253/63253]
real    0m2.780s
user    0m0.000s
sys     0m0.010s

serving a static file is way, way faster, so its not primarily a
network or dns issue.

some basic things - do you have APC enabled for php? if you don't,
apt-get install php5-apc, restart apache, and you'll get immediate
performance gains.

i'm not a wordpress dev, so i don't know if they have any devel
modules that can give you info about that sort of stuff, but i'd look
for one and see what it tells you. does wordpress have any basic,
built-in caching you could turn on?

if that's not an option, then you can use xhprof or xdebug to get some
raw numbers. failing that, just try to cut the problem in half a few
times with some simple debug patches to wordpress that just write
times to a log file so you can zero in on the low hanging fruit.

On 30 June 2010 09:37, Richard Ibbotson <[email protected]> wrote:
> On Wednesday 30 June 2010 00:25:24 Mike Lampard wrote:
>> I'd suggest the WP-Cache or WP-Super-Cache plugins, which
>> precompile the php to html so the server doesn't have to recompile
>> the pages on each access. The GZIP-Output wordpress plugin is also
>> recommended.
>
> I'll try those.  Meanwhile I've been hacking the DNS and bind9
> configuration.  Looks like it might have taken a second or two off the
> download time.  More like downloading a web page from planet earth
> rather than the moon :)

if you control all the moving parts, i'd suggest pushing the
compression further up|down the stack (depending on how you look at
it) to apache by using mod_deflate, rather than using php. you'll want
compression for your static files as well, and this is the simplest
and most cpu efficient way to get it.

cheers
justin
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to