Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 90795 invoked by uid 500); 24 Jul 2001 18:55:00 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 90783 invoked from network); 24 Jul 2001 18:55:00 -0000 Date: Tue, 24 Jul 2001 11:54:37 -0700 From: Justin Erenkrantz To: new-httpd@apache.org Subject: Re: OSDLab projectL Accept() locking on large (6+ CPU) boxes Message-ID: <20010724115437.M26972@ebuilt.com> References: <20010724110730.L28176@ebuilt.com> <3B5DBF39.2000609@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B5DBF39.2000609@pacbell.net>; from bpane@pacbell.net on Tue, Jul 24, 2001 at 11:32:25AM -0700 X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Tue, Jul 24, 2001 at 11:32:25AM -0700, Brian Pane wrote: > Are you able to observe this effect experimentally too? E.g., if > you run the threaded MPM on Solaris, does it use just one LWP per > process? Not with threaded MPM because it uses blocking system calls which allow Solaris's scheduler to jump in and rebalance. Initially, it'll be one LWP, but after some load hits, it should spawn multiple LWPs and rebalance the threads accordingly. However, try testthread on Solaris (with an MP box) and it'll execute all of the threads in serial rather than parallel. This is what drove me crazy last night - forcing me to comb through the manpages until I hit upon the pthread_setconcurrency call. By leveraging the pthread_setconcurrency call, the threads are balanced across LWPs immediately rather than waiting for each thread to hit a blocking system call or yield. -- justin