httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Bloom <>
Subject Re: newbie thread/process model question in hybrid server
Date Tue, 06 Jul 1999 11:52:09 GMT

Wow.  That's the big advantage of the hybrid server.  It also looks like
the hybrid approach is MUCH more scalable than either process or thread
based.  At least it is on any of the platforms we have looked at.


On Tue, 6 Jul 1999, Brian Havard wrote:

> On Tue, 6 Jul 1999 07:08:30 -0400 (EDT), Ryan Bloom wrote:
> >Actually, the argument for a hybrid approach has nothing to do with memory
> >leak.  That is the argument for a static number of threads.  The argument
> >for a hybrid server, is reliability.  Threads go down, just like processes
> >do, but when a thread goes down, so do the rest of the threads in the
> >process.  I have yet to see an OS that can recover a process when one of
> >it's threads dies unexpectedly.
> OS/2 can (I wrote a test program to prove it actually works too). Is this the
> only benefit of the hybrid approach? In OS/2 I can trap segfaults (and any
> other kind of fatal error) in an exception handler which can simply terminate
> the thread, possibly after doing some cleanup. It can also detect reentry
> into the exception handler so that if the cleanup segfaults it doesn't end up
> in an endless loop.
> Because of this I suspect that I can do a purely threaded approach and will
> start doing an MPM for it once I figure out how to do that :)
> --
>  ______________________________________________________________________________
>  |  Brian Havard                 |  "He is not the messiah!                   |
>  |  |  He's a very naughty boy!" - Life of Brian |
>  ------------------------------------------------------------------------------

Ryan Bloom
4205 S Miami Blvd	
RTP, NC 27709		It's a beautiful sight to see good dancers 
			doing simple steps.  It's a painful sight to
			see beginners doing complicated patterns.	

View raw message