apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Reid" <dr...@jetnet.co.uk>
Subject Re: [PATCH/CONTRIB] Shared Mem Hash Table
Date Thu, 05 Jul 2001 21:59:25 GMT
OK, to comment on this prior to the patch being posted...

I have SMS running as pools and the implementation I have manages to run the
server at 80% of the speed of pools.  This is with no changes to the httpd
code except using --enable-sms on the configure line.  Now, this isn't
amazing, but does present a starting point.  As I said we haven't started
optimising or altering.

We've found a load of problems and I'd like to Thank ben L for his support
and IRC server while Sander and I discussed/debated/debugged these problems
online this week.  We've been using Electric Fence to try and find problems
and it's worked well for us, so maybe we'll add it as an option to
configure?  Fixes have been committed for some of these and more will likely
be on the way.  Thoughts?

However, the fact remains that SMS after only a couple of months is ready
for use in httpd albeit with a performance penalty.  Platform known to work
was FreeBSD 4.3 and prefork MPM.  The code used was less tha  ideal and
faster code is on the way :)  By the time the patch gets to you all on
saturday I hope it'll be a bit quicker, but as a starting point it throws up
some issues :)

I'm in Dubai at the moment and after the frenetic pace of the last couple of
days I plan to take some time off in the morning round the pool :)

Does that whet your appetites enough?

Basically, we need more eyes looking at the code/implementations as soon as
possible, and this patch may enable that :)

Sorry Justin, have to be patient! (Not one of your strong points I know)
Small matter of getting connectivity without it costing me a fortune before
I commit :)


> On Thu, Jul 05, 2001 at 08:36:24AM -0700, Ian Holsman wrote:
> > In the conversations I have seen SMS was always talked about post 2.0
> > Release.
> > Is this still the case?
> Nah.  I think SMS is getting very close to being ready for more people
> to play with.  In order to solve some problems, we're going to have to
> use SMS.  David and Sander have made lots of progress with this.  (As
> I said, I spent yesterday going over the SMS code...)
> David just got an httpd up that uses no pools, but just SMS.  I believe
> that the API is identical from pools to SMS, but I'm not sure.  He has
> all of the details.  I'd bet the pool creation API might be slightly
> tweaked.
> Now that we can get an httpd up and serving pages, that means it now
> needs more people playing with it - i.e. starting to enable this in the
> mainline code.  It might be a configure time option in the short term
> so we don't screw everyone, but I think it'll be happening fairly soon.
> -- justin

View raw message