httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@covalent.net>
Subject Re: [PATCH] Eliminate HARD_THREAD_LIMIT on Windows
Date Sat, 22 Dec 2001 22:21:31 GMT
From: "Bill Stoddard" <bill@wstoddard.com>
Sent: Saturday, December 22, 2001 2:51 PM


> We would be best served by having an event driven/async MPM for scalability rather than
> pursuing the thread-per-connection model.

Agreed ... however; that doesn't diminish the benefit of multiple processes.

> Getting two (or more) Windows processes accepting connections off the same listening
> socket is certainly possible, but the cross process mutex that will be required to
> serialize the accepts will likely be a performance killer.  What works well on Unix
> probably will not be optimal on Windows. I could probably work something up in an hour
or
> so.

That sort of presumes that we might encounter the thundering hurd issue
on Windows.  I suspect, based on other, earlier experiments that this
won't be a problem.  Especially with the AcceptEx semantic.  The scoreboard 
itself doesn't need any mutexing, so that leaves this pretty vanilla.

If you want to pursue some other optimizations, that would be very cool.
I won't start pounding on this in the next few days, so anything you are
experimenting with won't get in my way.

I suspect there is a magic number in the threshold of how many listeners
and workers that a given worker-dispatch thread can optimially service.
Leaving the process entity around [multiple processes, that is] should help
us significantly.



Mime
View raw message