[wp-hackers] opcode caching + page caching plugin
steve at sltaylor.co.uk
Sun Jul 29 20:49:32 UTC 2012
> Easy answer: You should *always* use opcode caching for any PHP deployment,
> otherwise you're just repeating the process of parsing your code every
> request. Do make sure you've given enough shared memory to APC to keep all
> of your code cached.
I guess I just wondered what use is the opcode caching would be if
you're mostly serving flat cache HTML? OK, you'll speed up that page
cache refresh and admin access. But is that so important unless you
have a very high traffic site?
Page caching leveraging APC is a fair point for using both, but again
I'm just wondering if adding APC as well might be overkill for us.
One of our developers is questioning the fact that we need to manually
run a script every time we update code to refresh the APC cache. If
we're not getting worthwhile gains from APC, is this extra step to
remember worth it?
I feel like there's a lot of "how long is a piece of string" questions
buried in all this. Or is having APC + page caching more of a
no-brainer than I'm making out?
More information about the wp-hackers