Speedycgi

RT Users
1

Hi everyone,

I read in the docs that speedycgi is not supported yet. Is there any of
you who use it effectively in a production environment? Is it really
much faster than fastcgi and mod_perl?

Furthermore, does fastcgi work much faster and as well as mod_perl?

(I use RH7.3 , Apache/1.3.20 with mod_perl , MySQL)

Regards,

Rehan van der Merwe

2

Hi,

In article 1044520009.4413.73.camel@localhost.localdomain,Rehan van der Merwe rehan@nha.co.za wrote:

I read in the docs that speedycgi is not supported yet. Is
there any of you who use it effectively in a production
environment? Is it really much faster than fastcgi and
mod_perl?

yes, I have 2 boxes set up with RT running as SpeedyCGI. One
of them has intermittent problems, but it is probably not a
SpeedyCGI issue since that box has other problems as well.

I can’t comment about SpeedyCGI vs mod_perl, since neither box
runs Apache. However, as for FastCGI vs SpeedyCGI, SpeedyCGI is
easier on the administrator for a couple of reasons:

  1. You can tune SpeedyCGI for max number of scripts, max times
    each script can run, etc; you can’t do this with FastCGI.

  2. When the web server exits/dies/crashes, FastCGI processes
    stay in memory, but won’t be reused by the web server when it
    is restarted. I.e., if your web server dies a few times, you
    can have dozens of “zombie” FastCGI processes filling up your
    memory.

Ambrose LI Cheuk-Wing a.c.li@ieee.org

3
  1. You can tune SpeedyCGI for max number of scripts, max times
    each script can run, etc; you can’t do this with FastCGI.

FastCgiServer /path/to/foo -processes 6

  1. When the web server exits/dies/crashes, FastCGI processes
    stay in memory, but won’t be reused by the web server when it
    is restarted. I.e., if your web server dies a few times, you
    can have dozens of “zombie” FastCGI processes filling up your
    memory.

Oh? Never happened here…

dorfl# ps axwu | grep -c fcgi
1
dorfl# apachectl stop; apachectl startssl
/usr/local/sbin/apachectl stop: httpd stopped
/usr/local/sbin/apachectl startssl: httpd started
dorfl# ps axwu | grep -c fcgi
1
dorfl#

Phil Homewood, Systems Janitor, www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

4

In article 20030207034337.GF483@luggage.internal.moreton.com.au,Phil Homewood pdh@snapgear.com wrote:

Ambrose LI acli@ada.dhs.org via forwarder wrote:

  1. You can tune SpeedyCGI for max number of scripts, max times
    each script can run, etc; you can’t do this with FastCGI.

FastCgiServer /path/to/foo -processes 6

  1. When the web server exits/dies/crashes, FastCGI processes
    stay in memory, but won’t be reused by the web server when it
    is restarted. I.e., if your web server dies a few times, you
    can have dozens of “zombie” FastCGI processes filling up your
    memory.

Oh? Never happened here…

Oh… my web server has sub-par FastCGI support then :sunglasses:
(Well, I know it, but didn’t know it is that bad.)

Well, then forget about my comments if you use Apache…

Ambrose LI Cheuk-Wing a.c.li@ieee.org