Issac Goldstand wrote:
I think I got it... I was under the understanding that each fireman
could
only hande 1 bucket at a time, but there could be up to as many buckets
as
firemen on the stack at any given time... Do you know why it's like
that?
a limitation of the current mpms, there
Well, it's been getting *WAY* OT - more geared for dev@httpd if anywhere,
but I'm sure they've argued this out already :-) My initial ideas all
counted on the fact that each handler/filter would have a way of getting its
own per-request thread...
On the opposite, IMHO this is very ON topic,
- Original Message -
From: Stas Bekman [EMAIL PROTECTED]
Cc: Ask Bjoern Hansen [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, November 28, 2002 11:07 AM
Subject: default Content-Length calculation has been removed in 2.0 (was Re:
mod_perl 2.x vs. mod_perl 1.x benchmarks)
Actually
[Issac's view snipped]
Rather than commenting on your view Issac, please allow me to try again
to explain how I think it works, hopefully more clear this time:
Let's forget for a moment about buckets inside bridades, and call the
brigades themselves entities that are passed along.
Now think
.--[ Ask Bjoern Hansen wrote (2002/09/19 at 01:47:39) ]--
|
| On Wed, 18 Sep 2002, Josh Chamas wrote:
|
| [...]
| So I run it again with ServerTokens Min, and get the same results. :)
| Still something different on the mod_perl headers, looks like mod_perl
| 2.x is
On Wed, 18 Sep 2002, Josh Chamas wrote:
[...]
So I run it again with ServerTokens Min, and get the same results. :)
Still something different on the mod_perl headers, looks like mod_perl
2.x is setting Content-Length where it didn't use to.
The details evade me, but I recall something about
On the Apache 2.0 note, 2.0 breaks terribly when it has to
proxy chunked data. It strips the chunk length and does
not replace it with a Content-Length.
Bug is filed but no one in the Apache group seems to want
to play with it :(
Just a warning for those of you who may potentially be
doing
Hey mod_perl users,
I just did a benchmarks to compare mod_perl + apache versions 1 2.
What I find striking is that without any optimizations, the v2
mod_perl apache are faster. I'm really blown away, as I was
expecting the new versions to be slower with v1 configurations.
Here's the numbers
Josh Chamas wrote:
I just did a benchmarks to compare mod_perl + apache versions 1 2.
Cool.
Any idea why bytes/hit is lower on apache 2? Are some headers being
omitted?
- Perrin
Perrin Harkins wrote:
Josh Chamas wrote:
I just did a benchmarks to compare mod_perl + apache versions 1 2.
Cool.
Any idea why bytes/hit is lower on apache 2? Are some headers being
omitted?
Looks like its the Server tokens, see below. 32 bytes!
Maybe on a benchmark this small,
10 matches
Mail list logo
