[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: FastCGI daemon
- From: Stefan <stefan@...>
- Date: Fri, 23 Oct 2009 12:53:05 -0700
Fabio Mascarenhas wrote:
On Fri, Oct 23, 2009 at 3:33 PM, Stefan <firstname.lastname@example.org> wrote:
Jacob Jay wrote:
FastCGI is definitely the way to go, but if you haven't, do check out
wsapi-fcgi which is part of Kepler (http://keplerproject.org/). I use this
with spawn-fcgi and lighttpd/nginx. An additional FCGI-Lua interface may be
unnecessary unless you want it to do something notably different to that of
the Kepler WSAPI one.
I was under the impression that wsapi-fcgi did NOT persist the scripts
between invocations, unless you run each script as it's own fastcgi server.
Running a couple dozen (at least) extra processes that MUST stay up at all
times doesn't appeal to sysadmin in me.
The generic wsapi.fcgi launcher does persist scripts (and each script
is isolated in its own Lua state), but each wsapi.fcgi process can
only serve a single request at a time, so you need to configure your
web server to keep multiple wsapi.fcgi workers to service concurrent
requests. wsapi.fcgi also reloads the script in a fresh Lua state if
the underlying file has been modified.
So, does this mean that if you had say - 60 scripts - and were running 3
launchers, you would end up with a total of 180 Lua states (and
connections to the DB or other backend storage)?