Bill Stoddard wrote:
I guess for some definition of much I am not suprised. I would expect
the event MPM to consume more CPU than worker under 'low' workloads (low
number of concurrent clients)
I was only testing with about 1024 concurrent clients. In production,
we see about 4k.
--
On Sep 9, 2005, at 4:25 PM, Brian Pane wrote:
This weekend, when I have time to do some more httpd work, I'll do
a more
robust hack of the leader MPM within the async-dev branch so that it's
available for other people to test.
Just committed... This version is a bit slower than the worker
Brian Akins wrote:
I have been testing 2.1 in our environment. So far, so good. I was
especially testing the prosy stuff (proxy, http, and balancer). Very
good stuff.
Good to hear!
The event MPM is much slower in our case.
We may or may not ship the event MPM. Our new release model
On Fri, Sep 09, 2005 at 04:18:34PM -0400, Bill Stoddard wrote:
I guess for some definition of much I am not suprised. I would expect the
event MPM to consume more CPU than worker under 'low' workloads (low number
of concurrent clients) because it's making more system calls to do the same
Colm MacCarthaigh wrote:
On Fri, Sep 09, 2005 at 04:18:34PM -0400, Bill Stoddard wrote:
I guess for some definition of much I am not suprised. I would expect the
event MPM to consume more CPU than worker under 'low' workloads (low number
of concurrent clients) because it's making more
On 8/9/05, Ian Holsman [EMAIL PROTECTED] wrote:
cost of devoting a senior engineer for the next month or two to help
'field test' apache 2.2 in a high scale environment, identifying and
submitting patches to 2.2 is Y.
Just wondering, when will Win32 binaries of 2.1/2.2 be available for
As I sit here debugging our home grown proxy code for 2.0, I wonder how long
until 2.2? We wrote our own proxy because the cool 2.1 stuff was not out at
the time. The new proxy stuff would be wonderful for us, but noone wants to
run alpha code in production. (However, we are quick to run
Akins, Brian wrote:
As I sit here debugging our home grown proxy code for 2.0, I wonder how long
until 2.2? We wrote our own proxy because the cool 2.1 stuff was not out at
the time. The new proxy stuff would be wonderful for us, but noone wants to
run alpha code in production. (However, we
Akins, Brian wrote:
As I sit here debugging our home grown proxy code for 2.0, I wonder how long
until 2.2? We wrote our own proxy because the cool 2.1 stuff was not out at
the time. The new proxy stuff would be wonderful for us, but noone wants to
run alpha code in production. (However, we
