[wp-hackers] 2.next - faster

Scott johnson fuzzygroup at gmail.com
Tue Feb 7 07:02:25 GMT 2006

Correct.  While I hate to say "wait for people to upgrade to php5",
the opcode cache is standard (from what I know) in php5.  Waiting for
people to upgrade to php5 would save a lot of engineering effort.

Note: I hate to NOT be definitive on something like this but most of
my experience is in php 4.1.x since that's what our systems ran.  That
said when we moved to APC and were able to use it (not always) we did
see a reliable 50%+ improvement.  The reasons we didn't run it as a
standard were more us than anything else.


On 2/6/06, Matt Mullenweg <m at mullenweg.com> wrote:
> David House wrote:
> > Most of the time taken for WordPress to load is down to the long time
> > needed for PHP to parse the thousands of lines of code, IIRC.
> Yep, and an opcode cache helps a HUGE amount here. So much that it might
> not be worth optimizing for this case for the very small percentage of
> users that need that performance but can't run an opcode cache.
> --
> 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

J. Scott Johnson
Ookles launches 2/28/06 - have you signed up yet?
new startup: http://ookles.com/
blog: http://fuzzyblog.com/
podcast: http://techwarstories.com/
fuzzygroup at gmail.com
aim: fuzzygroup
cell: 857 222 6459

More information about the wp-hackers mailing list