I put up Apache 2.2.2 (S)RPMS if anyone is interested.
http://peruser.xservu.com/repo/
Seem to work quite stable. They'r based on FC5 RPMS and peruser patch
has been modified to go /w new 1.2.x Apache Portable Runtime (APR). Also
Apr packages are included in the same folder. Binary packages have been
built on centos 4.3.
Heres my report of how's it have worked out for me:
* mod_fastcgi DOES NOT seem to work with peruser.
- server seem to crash quite fast and some php processes seem to
hang somewhere in between.
- many segmentation fauls occur
- server stops responding if heavier load applied.
* mod_fcgid /w rommer patches seem to work fairly well, but i wouldn't
call it satisfactory
- doing graceful restart seem to produce many segmentation faults
- my current php5 server (/w mod_php & mod_fcgid) gives 30-50
segfaults a day (~200 000 reqs/day), but only 10% of traffic is produced
by fcgi domains. Segaults come with: [info] (107)Transport endpoint is
not connected: apr_socket_addr_get(APR_REMOTE)
- segfaults CANNOT be reporduced using apache bencmark. Hit 4 000
000 requests using concurrency 1, 20, 300 and server dropped only very
few requests and also did NOT produce any segmentation faults whatsoever.
* my current php4 server (/w mod_php) gives 3-5 segmentation faults a
WEEK (~45 000 reqs/day)
- GRACEFUL works better, but still gives some segfaults if enough
virtual hosts configured.
* things I could not pin to any above categories:
- after using graceful on server, more and more child seem to
segment. fault until server stops responding.
If I do GRACEFUL at least twice a day it could end up with
1500 segfaults a /day and if unlucky enough server stops responding.
Things seem be worse then mod_fcgi is being used on server, but
is not a proven fact.
Hope it could be useful to someone
_______________________________________________
Peruser mailing list
[email protected]
http://www.telana.com/mailman/listinfo/peruser
