[wp-hackers] 5 minutes to a faster blog
h0bbel at p0ggel.org
Fri Dec 1 10:23:16 GMT 2006
I run 2.1-svn on eAcc 0.9.6-svn without problems at all.
Has the "bleeding edge" idiot I am, I also run Apache 2.2.3, PHP 5.2.0 and it all works just fine.
I did try to follow Matt's suggestions though, and there were a couple of tables in the wp database I could not convert from MyISAM to InnoDB, namely "wp_posts" and "wp_comments". I got "#1214 - The used table type doesn't support FULLTEXT indexes" when trying to convert them?
Christian aka h0bbel
On Fri, 1 Dec 2006 11:53:00 +0200, Computer Guru <computerguru at neosmart.net> wrote:
> What about eAccelerator? That's what I'm currently using and what everyone
> is recommending out there.. Is it the same thing?
> I can't remember, but once when googling I came across a link that said WP
> was "purposely making it hard to use eAccelerator" [sic] and preferred
> Is it recommended to use APC with WP over eAccelerator?
> Computer Guru
> NeoSmart Technologies
>> -----Original Message-----
>> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
>> bounces at lists.automattic.com] On Behalf Of Matt Mullenweg
>> Sent: Friday, December 01, 2006 11:52 AM
>> To: wp-hackers at lists.automattic.com
>> Subject: [wp-hackers] 5 minutes to a faster blog
>> With the following I regularly get sub 100 millisecond front-page
>> generation time on photomatt.net, and lower on WP Pages. No caching
>> plugins, no alternative front-ends that make me rewrite my themes and
>> plugins, just plain WordPress.
>> 1. Use APC:
>> APC can give you a 3x speedup in load times, instantly.
>> Tip: If you're on Litespeed, use this to save memory:
>> (APC is bundled with Litespeed, btw.)
>> 2. Enable the query cache:
>> nano /etc/my.cnf
>> query_cache_size = 64M
>> /etc/init.d/mysql restart
>> This usually cuts in half most SQL times on busy sites, if not more.
>> 3. Swich your tables to InnoDB
>> Use phpMyAdmin > table > Operations to switch.
>> And add the following in your MySQL config file, adjust sizes as
>> necessary for your memory:
>> # Make buffer_pool larger than the size of your DB, if possible
>> Restart MySQL.
>> 4. Enable WP's built-in caching
>> define( 'ENABLE_CACHE', true ); // in wp-config.php
>> Unless you have slow HDs, like a NFS-based host like Dreamhost.
>> == More than 5 minutes, bonus ==
>> 5. Use WP 2.1
>> It's way faster.
>> Matt Mullenweg
>> http://photomatt.net | http://wordpress.org
>> http://automattic.com | http://akismet.com
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers