-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Travis (wikiHow) wrote:
Great, that makes total sense and seems to have worked
well. I think it
looks like for article views, 1.12 is performing better than 1.9 now, thanks
for the help.
For opcode caching, we're using eaccelerator, should we be using something
else? What does WP use?
We use APC; last I looked eaccelerator was pretty flake on PHP 5,
especially 5.1 and later, but that might have changed. YMMV. :)
Also, I noticed that the PHP sapi name for WP is just
apache, while ours is
apache2handler. Could there be a difference in terms of performance between
the 2? How do you go about creating just an apache module?
As I recall...
apache = Apache 1.3 module
apache2 = Apache 2.0 module
apache2handler = Apache 2.0 module using a different Apache API
There's probably not a huge difference in performance, but again YMMV. :)
If in doubt, try them out.
- -- brion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iEYEARECAAYFAkhNdNYACgkQwRnhpk1wk47IdACfVOiwG5DUGprQBQZ3PE8/xV0g
9hkAoMeew8am9JD7ha5Yp3yYA9YExuYU
=mWxa
-----END PGP SIGNATURE-----