You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Justin Erenkrantz <je...@ebuilt.com> on 2001/09/08 20:33:48 UTC

General Availability release qualities?

Since a lot of people on-list are starting to make noise about
rejecting feature changes because we are close to releasing
Apache 2.0, I would like to ask what are the outstanding issues
that must be addressed before we release Apache 2.0 as GA?

As a starting point, my personal items are as follows:

- Completely remove threaded MPM and replace it with worker.  I do
  not think that the current threaded MPM can work (due to discussions
  held on this list previously).  The worker MPM (which Aaron has been 
  making progress towards) should act as a replacement MPM.  I know
  that Aaron has some patches that he has tested that make it faster
  than prefork.  I look forward to seeing those patches make it in
  and fully tested.

- Get the APR lock situation straightened out.  This means converting
  the old lock API to the new one.  (This probably means that APR
  needs to at least be beta by the time we release httpd as GA - other
  than the locks, I don't see that as a major problem.  I don't want
  to have any major API changes after we hit GA - the lock API is a
  fairly major API in APR.)

- Get mod_ssl stable - which at this point, requires testing it.
  I was under the (false) impression that mod_ssl wasn't going to 
  hold up any releases.  Since OtherBill said that isn't true, 
  let's make sure it is rock solid.  This probably means that 
  we need to get a few beta-quality tarballs before going GA.
 
- Resolve the proxy situation.  A lot of committers (FirstBill
  comes to mind) would like to see this come back in the core.  
  If it is ready and the group consensus is to add it, then let's
  add it back in before GA.
 
- Make sure that the recent optimizations in mod_include didn't
  bust anything.  I don't think it did (otherwise, I wouldn't have
  committed it), but it does need to be tested.  We can probably
  strengthen the tests in httpd-test to create bucket border cases.

- Straighten out the filter config syntax as OtherBill and I have 
  suggested.  I think that the current syntax is too confusing and
  not powerful enough.  Once we release httpd-2.0 as a GA, I don't 
  think we can make any configuration syntax changes.  So, this 
  would have to go in before we hit GA.

- Verify the bucket/brigade API and potentially try to address the
  memory usage concerns (get it not to do malloc/free on small 
  chunks).  AIUI, Cliff is working towards this.

- Update the documentation to be as current as we can make it.  I
  think that the docs are fairly up-to-date, but we need to make
  sure that the docs are just as solid as the code.  

- I would like to see performance with Apache 2.0 equal or surpass
  the performance of Apache 1.3.  However, I'm not entirely sure
  that will happen before we can release (if you want to do so in
  45 days as some have suggested).  Given that that may not be the
  case, I'd like it to be as close as possible.  In the last few
  weeks, we've definitely made strides towards improving our
  performance (especially in mod_include - thanks to Brian and Ian).
  In the subsequent point releases, we can continue to address the 
  overall performance and attempt to make 2.1 faster than 1.3.  
  However, if 2.0 isn't faster than Apache 1.3, I wonder how many 
  people will adopt it (however, most sites are bandwidth limited, 
  so I'm not sure if this is a concern).  Therefore, I think we 
  need to come to a consensus about our take on the performance of 
  Apache 2.0 relative to Apache 1.3.  Is it a requirement that 
  Apache 2.0 must be as fast as Apache 1.3 before we hit GA?  

I believe that our current tree status is at a beta-quality level.  
And, I think we can start to see the light at the end of the tunnel
(and are anxious to get this released and out the door).  People 
can use it, but I'm not entirely sure that I would call what we 
have as being rock-solid as Apache 1.3.

Before we release a GA build, I believe *we* have to believe that it 
is a substantially better and as reliable a product as Apache 1.3 
(which is a very hard product to beat).  This doesn't mean that
there aren't any bugs with it - it's just that we know of *zero* 
bugs in the tree after receiving all of the feedback from the 
community, testers, and our own use.

I would like to ensure that any GA is ready and that we can 
encourage any site admin who runs Apache 1.3 that they can upgrade 
to 2.0 without any loss in functionality or stability (provided
that their modules are ported properly).

As most of you know (like I haven't said it enough), I'm going to be 
out of regular email contact for a few weeks.  But, I hope this 
enlightens you on my perspective on what should happen before a 
GA is released.  I look forward to seeing any replies and thoughts 
before I leave tomorrow (please continue this thread even if I can't
reply!).  

"How do we know when we get there if we don't know where we're going?"

Once classes start again and I get settled in my new place, I'll 
resume active development.  -- justin


Re: what about proxy?

Posted by Graham Leggett <mi...@sharp.fm>.
Greg Stein wrote:

> I'm +1 on creating httpd-rollup, and -0.5 on putting proxy back in.

Ok - first question - what do we call the rollup release:

o Option A: apache-2.x.x.tar.gz

  Combines httpd-2.0, apr, apr-util, httpd-proxy and
  httpd-ldap and produces an apache rollup tree.

o Option B: apache-2.x.x.tar.gz, apache-modules-2.x.x.tar.gz

  Combine httpd-2.0, apr, apr-util into apache-2.x.x.tar.gz,
  and combine httpd-proxy, httpd-ldap into apache-modules-2.x.x.tar.gz.

o Option C: apache-2.x.x.tar.gz, apache-proxy-2.x.x.tar.gz,
  apache-ldap-2.x.x.tar.gz

  Combine httpd-2.0, apr, apr-util into apache-2.x.x.tar.gz, 
  and combine httpd-proxy into apache-proxy-2.x.x.tar.gz, and
  combine httpd-ldap into apache-ldap-2.x.x.tar.gz.

o Option D: something else...

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Re: what about proxy?

Posted by Greg Stein <gs...@lyra.org>.
On Tue, Sep 11, 2001 at 04:11:16AM -0400, Chuck Murcko wrote:
> 
> On Tuesday, September 11, 2001, at 04:01 AM, Graham Leggett wrote:
> 
> >> Rather than doing that, why don't we work on the rollup mechanism 
> >> instead?
> >> Proxy has been moving along terrifically while in its own CVS module.
> >
> > We can do this too - but then I'd say we would need to finalise the
> > rollup release issue before we can go GA. Who is willing to sort out the
> > rollup release?
> 
> Most of the stuff to build a rollup release is already running in the 
> proxy builds.

My suggestion is to take what you learned in proxy, and establish the
httpd-rollup project (I posted on this earlier, something with "rollup" in
the subject).

Since you guys have already been doing it, then it makes sense to formalize
that into a project. The project would mostly just be some scripts and
things, but it could grab code from "anywhere" to roll together a release.

Hell... we haven't even started talking about bundling some of our Java and
XML tools with the web server. Lots of neat things that could happen there,
too.

I'm +1 on creating httpd-rollup, and -0.5 on putting proxy back in.

[ if (since?) mod_ldap is going out, then we have to deal with the rollup
  anyways, which would totally kill any impetus for putting proxy back in.
  thus, I'm against bringing proxy back into the core. ]

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Re: what about proxy? (was: Re: General Availability release qualities?)

Posted by Chuck Murcko <ch...@topsail.org>.
On Tuesday, September 11, 2001, at 04:01 AM, Graham Leggett wrote:

>> Rather than doing that, why don't we work on the rollup mechanism 
>> instead?
>> Proxy has been moving along terrifically while in its own CVS module.
>
> We can do this too - but then I'd say we would need to finalise the
> rollup release issue before we can go GA. Who is willing to sort out the
> rollup release?
>

Most of the stuff to build a rollup release is already running in the 
proxy builds.

Chuck

Re: what about proxy? (was: Re: General Availability release qualities?)

Posted by Graham Leggett <mi...@sharp.fm>.
Greg Stein wrote:

> When you say placeholder, are you suggesting that you're going to commit the
> code back into the httpd-2.0 branch?

Yes - in the last (long) discussion it got the needed +1's, but it was
never done.

I've delayed actually committing the thing yet to make sure people have
time to complain about me doing it :)

> Rather than doing that, why don't we work on the rollup mechanism instead?
> Proxy has been moving along terrifically while in its own CVS module.

We can do this too - but then I'd say we would need to finalise the
rollup release issue before we can go GA. Who is willing to sort out the
rollup release?

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

what about proxy? (was: Re: General Availability release qualities?)

Posted by Greg Stein <gs...@lyra.org>.
On Sun, Sep 09, 2001 at 02:16:25PM +0200, Graham Leggett wrote:
> Justin Erenkrantz wrote:
> 
> > - Resolve the proxy situation.  A lot of committers (FirstBill
> >   comes to mind) would like to see this come back in the core.
> >   If it is ready and the group consensus is to add it, then let's
> >   add it back in before GA.
> 
> As FirstBill said, adding it back received the needed +1's when it went
> to vote. After all the discussion had subsided though, it was simply not
> done.
> 
> As I said on thursday, later this evening I'll be comitting the proxy
> module to it's placeholder in the core.

When you say placeholder, are you suggesting that you're going to commit the
code back into the httpd-2.0 branch?

Rather than doing that, why don't we work on the rollup mechanism instead?
Proxy has been moving along terrifically while in its own CVS module.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Re: General Availability release qualities?

Posted by Graham Leggett <mi...@sharp.fm>.
Justin Erenkrantz wrote:

> - Resolve the proxy situation.  A lot of committers (FirstBill
>   comes to mind) would like to see this come back in the core.
>   If it is ready and the group consensus is to add it, then let's
>   add it back in before GA.

As FirstBill said, adding it back received the needed +1's when it went
to vote. After all the discussion had subsided though, it was simply not
done.

As I said on thursday, later this evening I'll be comitting the proxy
module to it's placeholder in the core.

Regards,
Graham
-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Re: General Availability release qualities?

Posted by Ryan Bloom <rb...@covalent.net>.
> This brings up a good point: What is satisfactory in terms of performance
> and features to release a 2.0 GA from this group?  How do we answer
> questions like "how much faster is it?" and "how well does it scale?" and
> "what new features do I have to look forward to?" To most people I don't
> think the last question will be at all obvious. The work from Brian,
> Ian, Justin, OtherBill, etc has done wonders for performance, but we're
> still not (by my calculations) anywhere near as fast as 1.3. How good
> is good enough? Some guidance here may help us newbies.

My own opinion?  We have to be at least as performant as 1.3, with prefork.
The threaded ones don't have to perform as well in terms of seconds to serve
a single request, but they do have to scale better than 1.3.

Now, how we measure this, is another question.  Oh, before anybody says that
we have already met these on Windows, I believe this must be the case on
Unix (any Unix, but Solaris, AIX, and Linux would be a good start) before we
are ready for GA.

I also believe that we need at least two more betas before we go GA.  I am the
guy who was agitating for a GA release first (about a year and a half ago), so 
everybody knows that I want this more than ANYBODY else in the world.  
However, we have made a lot of changes since 2.0.16, if we try to release a
production release without letting people play with it, we have done a MAJOR
dis-service to our users.

Ryan

______________________________________________________________
Ryan Bloom				rbb@apache.org
Covalent Technologies			rbb@covalent.net
--------------------------------------------------------------

Re: General Availability release qualities?

Posted by Aaron Bannert <aa...@clove.org>.
On Sat, Sep 08, 2001 at 11:33:48AM -0700, Justin Erenkrantz wrote:
[snip]
> - Completely remove threaded MPM and replace it with worker.  I do
>   not think that the current threaded MPM can work (due to discussions
>   held on this list previously).  The worker MPM (which Aaron has been 
>   making progress towards) should act as a replacement MPM.  I know
>   that Aaron has some patches that he has tested that make it faster
>   than prefork.  I look forward to seeing those patches make it in
>   and fully tested.

To keep everyone informed as to the status of the worker MPM (this would
be good stuff to put in the STATUS, maybe I'll provide a patch). I have
three implementations of worker that each do things a little differently.
I will be trying to acquire access to a large N-way SMP box in the near
future to test the scalability attributes of each variation.  Under an
artificial workload generated from flood, I have seen at least one of my
implementations perform on par with the perfork MPM.  There are still
some bugs to be worked out of the worker (It's having trouble with the
MaxClients directive right now), but I should have these figured out
soon enough. If we are able to produce a beta in the next week, I'll
shoot for a stable worker MPM by the next beta.


> - Get the APR lock situation straightened out.  This means converting
>   the old lock API to the new one.  (This probably means that APR
>   needs to at least be beta by the time we release httpd as GA - other
>   than the locks, I don't see that as a major problem.  I don't want
>   to have any major API changes after we hit GA - the lock API is a
>   fairly major API in APR.)

The new lock API itself is pretty straightened out, and we've been committing
bit-sized chunks over the last week or so. I expect the full API to be
commited in the next week, and maybe another week or so to get a full
implementation on the other non-UNIX platforms (as well as some good testing).
At that point we can do each of two things: 1) port the old API to use the
new one, and 2) port httpd to the new API.


[cut out a bunch of stuff that would be well suited for a STATUS]
 
> - I would like to see performance with Apache 2.0 equal or surpass
>   the performance of Apache 1.3.  However, I'm not entirely sure
>   that will happen before we can release (if you want to do so in
>   45 days as some have suggested).  Given that that may not be the
>   case, I'd like it to be as close as possible.  In the last few
>   weeks, we've definitely made strides towards improving our
>   performance (especially in mod_include - thanks to Brian and Ian).
>   In the subsequent point releases, we can continue to address the 
>   overall performance and attempt to make 2.1 faster than 1.3.  
>   However, if 2.0 isn't faster than Apache 1.3, I wonder how many 
>   people will adopt it (however, most sites are bandwidth limited, 
>   so I'm not sure if this is a concern).  Therefore, I think we 
>   need to come to a consensus about our take on the performance of 
>   Apache 2.0 relative to Apache 1.3.  Is it a requirement that 
>   Apache 2.0 must be as fast as Apache 1.3 before we hit GA?

This brings up a good point: What is satisfactory in terms of performance
and features to release a 2.0 GA from this group?  How do we answer
questions like "how much faster is it?" and "how well does it scale?" and
"what new features do I have to look forward to?" To most people I don't
think the last question will be at all obvious. The work from Brian,
Ian, Justin, OtherBill, etc has done wonders for performance, but we're
still not (by my calculations) anywhere near as fast as 1.3. How good
is good enough? Some guidance here may help us newbies.

[snip snip]

-aaron