Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache HTTPD Bugs Notification List" <bugs@httpd.apache.org>
From: bugzilla@apache.org
To: bugs@httpd.apache.org
Subject: [Bug 55581] New: Support concurrent connections to same FastCGI
 process
Date: Sun, 22 Sep 2013 01:05:20 +0000
Message-ID: <bug-55581-7868@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=55581

            Bug ID: 55581
           Summary: Support concurrent connections to same FastCGI process
           Product: Apache httpd-2
           Version: 2.5-HEAD
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: mod_fcgid
          Assignee: bugs@httpd.apache.org
          Reporter: ezyang@mit.edu

Currently, it appears that mod_fcgid's behavior when receiving a request is to
take a FastCGI process out of the pool, send it the request, and then put the
process back in the pool. While the request is being serviced, the application
is not available for other requests. If mod_fcgid notices that there are no
more processes left, it will spin up new processes.

This is not good behavior when the process is multithreaded, and can handle
concurrent requests. In such cases, mod_fcgid should *not* spawn new processes,
and just concurrently deliver them to the existing process. This allows the
server in the backend to take advantage of shared resources. Obviously this
should be configurable.

Here is an example of another user who wants this functionality:
http://stackoverflow.com/questions/15623422/mod-fcgid-multithreaded-fastcgi-now-or-in-a-planned-future

I would just like to get confirmation that this is indeed a enhancement the
core developers would take; our team is considering implementing this for our
own needs.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org