Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@minotaur.apache.org Received: (qmail 14769 invoked from network); 11 Feb 2011 13:35:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Feb 2011 13:35:22 -0000 Received: (qmail 73050 invoked by uid 500); 11 Feb 2011 13:35:22 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 72877 invoked by uid 500); 11 Feb 2011 13:35:20 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 72868 invoked by uid 99); 11 Feb 2011 13:35:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Feb 2011 13:35:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of info@bnoordhuis.nl designates 209.85.161.173 as permitted sender) Received: from [209.85.161.173] (HELO mail-gx0-f173.google.com) (209.85.161.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Feb 2011 13:35:12 +0000 Received: by gxk28 with SMTP id 28so1211022gxk.18 for ; Fri, 11 Feb 2011 05:34:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.136.21 with SMTP id j21mr545271ybd.407.1297431291358; Fri, 11 Feb 2011 05:34:51 -0800 (PST) Received: by 10.151.111.5 with HTTP; Fri, 11 Feb 2011 05:34:51 -0800 (PST) X-Originating-IP: [195.130.156.9] In-Reply-To: References: Date: Fri, 11 Feb 2011 14:34:51 +0100 Message-ID: Subject: Re: mod_ruby on Apache for Windows 2.2.17 From: Ben Noordhuis To: modules-dev@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Fri, Feb 11, 2011 at 14:11, Zeno Davatz wrote: >> Apache on Windows serves all requests from a single process. > > Apache on Linux does not do that? Nope. The worker and event MPMs are hybrids: serving requests from many processes, where each process has many threads. And if all processes are busy, Apache will simply spin up more. >> The Ruby interpreter is not thread-safe so mod_ruby creates a Big Mutex >> whenever it needs to run. Thus on Windows, with its single-process >> model, mod_ruby can only serve one request at a time. > > So you say, that mod_ruby on Windows can _not_ leverage its power > because Apache on Windows is a single thread process? Effectively single-threaded when mod_ruby is serving a request, yes.