No PHP benefit either way.
There's no reason to go to nginx for performance, but there's also no
reason not to use it.
Personally, I've got a preference for nginx, so I'm using it myself.
And for smaller sites not using a front end cache or multiple domains,
it is nice when you are serving out the /images folder with the same
webserver.
So, no nginx performance benefit for MediaWiki. But there's no real
benefit of Apache over other webservers either.
~Daniel Friesen(Dantman, Nadir-Seen-Fire) of:
-The Nadir-Point Group (
http://nadir-point.com)
--It's Wiki-Tools subgroup (
http://wiki-tools.com)
--The ElectronicMe project (
http://electronic-me.org)
--Games-G.P.S. (
http://ggps.org)
-And Wikia ACG on
Wikia.com (
http://wikia.com/wiki/Wikia_ACG)
--Animepedia (
http://anime.wikia.com)
--Narutopedia (
http://naruto.wikia.com)
Aryeh Gregor wrote:
On Tue, Aug 26, 2008 at 11:28 AM, howard chen
<howachen(a)gmail.com> wrote:
But there are still a number of pages which
cannot be cached by Squid?
Even pages that aren't cached by Squid are still proxied through it.
It proxies all requests, and caches those that are cacheable. No one
outside Wikimedia's internal network is ever communicating directly
with an Apache or lighttpd server when using the Wikimedia projects,
to my knowledge. (lighttpd is in fact used by the image servers,
incidentally.)