Hi Josh,
How about the dual setup, a plain Apache + a mod_perl
Apache, which some mod_perl sites are based on? Another
interesting candidate is fastCGI.
Peter
We get very similar numbers in our benchmarking. Please see
the benchmarks I have published on this at:
http://chamas.com
. Basically, I'd like to put mod_proxy behind the load balancer and
allow the proxy servers to talk to the mod_perl servers. Unfortunately, the
load balancer does not allow for sticky sessions and only bounces the user
round-robin style. I am playing with the idea of sending a cookie down
[EMAIL PROTECTED] wrote:
But you're not accounting for the possibility of server
failure on the backend. A proper load-balancer
(including the open source ones and
mod_backhand) would detect dead servers and handle the
failover to
another server.
This is true. Then one has to ping the
Interesting but isn't the difference within
statistical fluctuation ? :-)
Did you compare them to the pure C module (without embed
Perl)?
Peter Bi
If I compiled a c module that embed a perl interpreter and
I benchmark this again the same module in mod_perl
I got a big difference
Ken:
back to your original problem. Maybe you should disbale
the default index list by comment out Options Indexes
in your httpd.conf, so as to isolate the problem: if it
is authz related or not at all.
Peter
A note: since cookie is involved, why not to implement
all the
A note: since cookie is involved, why not to implement
all the access/authentication/authurization functions at
the access control phase using cookie ?
Peter
I've got an interesting problem, related to my development of some
Authen/Authz handlers.
I have a directory on which I've
Maybe you can tell us more about the project (e.g. why
telnet ?) so there will come many bad advices ? :-)
Peter Bi
Perrin wrote:
I can't see how it could be working now
That makes two of us!
You're probably opening new telnet connections from each apache process.
I know that I
Hi Jay, Perrin, and Geoff,
Thanks for your thoughts on this problem.
Jay yohimbe Thorne wrote:
For what its worth, I'd recommend KeepAlive Off for almost any mod_perl
deployment. It basically is a waste of memory and a process slot.
Especially
if you put graphics on a separate server.
My
Hi,
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process often doesn't exit right
[EMAIL PROTECTED] writes:
I'm using Apache::SizeLimit (on both Solaris and Linux) and getting the
error_log entry:
[Tue Dec 11 15:01:19 2001] (2520) Apache::SizeLimit httpd process too
big,
exiting at SIZE=44964 KB SHARE=10900 KB REQUESTS=389 LIFETIME=9505
seconds
But the child process
10 matches
Mail list logo