[wp-hackers] 5 minutes to a faster blog

[Computer Guru]

Oh ok.
I have Gallery2 as well... good thing you warned me :)

Computer Guru
NeoSmart Technologies
http://neosmart.net/blog/


> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of Christian Mohn
> Sent: Friday, December 01, 2006 1:03 PM
> To: wp-hackers at lists.automattic.com
> Subject: RE: [wp-hackers] 5 minutes to a faster blog
> 
> I haven't compared eAcc with APC, as APC is known to have problems
> dealing with Gallery 2. That being said, APC does have "the right
> people" behind it, eg. Rasmus Lerdorf so I wouldn't be that surprised
> if it performs better.
> 
> Christian
> 
> On Fri, 1 Dec 2006 12:38:25 +0200, Computer Guru
> <computerguru at neosmart.net> wrote:
> > Yeah, you can't use FULLTEXT (used for advanced search options) with
> > InnoDB, only with MyISAM.
> >
> > I too use the same config, except with II6 and IIS7 instead of
> Apache.
> >
> > I know eAccelerator /works/ with WP, my only question is if APC works
> > /better/ with it.
> >
> > Computer Guru
> > NeoSmart Technologies
> > http://neosmart.net/blog/
> >
> >
> >> -----Original Message-----
> >> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> >> bounces at lists.automattic.com] On Behalf Of Christian Mohn
> >> Sent: Friday, December 01, 2006 12:23 PM
> >> To: wp-hackers at lists.automattic.com
> >> Subject: RE: [wp-hackers] 5 minutes to a faster blog
> >>
> >> 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
> >> > APC.
> >> > Is it recommended to use APC with WP over eAccelerator?
> >> >
> >> > Computer Guru
> >> > NeoSmart Technologies
> >> > http://neosmart.net/blog/
> >> >
> >> >
> >> >> -----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:
> >> >>
> >> >> http://pecl.php.net/package/APC
> >> >>
> >> >> APC can give you a 3x speedup in load times, instantly.
> >> >>
> >> >> Tip: If you're on Litespeed, use this to save memory:
> >> >>
> >> >>
> >>
> http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:ph
> >> >> p:opcode_cache
> >> >>
> >> >> (APC is bundled with Litespeed, btw.)
> >> >>
> >> >> 2. Enable the query cache:
> >> >>
> >> >> nano /etc/my.cnf
> >> >>
> >> >> [mysqld]
> >> >> ...
> >> >> 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
> >> >> innodb_buffer_pool_size=512M
> >> >> innodb_additional_mem_pool_size=20M
> >> >> innodb_flush_log_at_trx_commit=0
> >> >> innodb_log_buffer_size=8M
> >> >>
> >> >> 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
> >> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> >
> >> > _______________________________________________
> >> > wp-hackers mailing list
> >> > wp-hackers at lists.automattic.com
> >> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >>
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers