Paul A Houle wrote:
Jess Holle wrote:
So if one uses worker and few processes (i.e. lots of threads per),
then Solaris should be fine?
That's what people think, but I'd like to see some numbers.
I've never put a worker Apache into production because most of our
systems depend on PHP or something else which I wouldn't trust 100% in
a threaded configuration.
That's understandable if you're in that boat.
We bundle and support our own Apache builds with our products. Our only
dynamic content comes from mod_jk (and thus will come from the proxy AJP
module in 2.2), so threading is all well and good. Given that most of
our content is dynamic and thus via AJP, Apache performance is never
really the issue -- if anything above the application code itself is
ever an issue it is the extra hop involved with AJP, but there are clear
load-balancing, security, etc, benefits from this architecture.
Customers seem to consistently assume that using Apache is giving
(substantively) lower overall performance than they'd get with something
else, though -- chalk that up to good marketing by Microsoft, Sun, et al.
As for the big file issue you note, that would only seem to be a big
issue when coupled with slow connections -- which are getting rarer
these days -- and much more of an issue with prefork than worker.
--
Jess Holle
