Re: [Openinteract-dev] Using FastCGI as development plaftorm

[Perrin H. <pe...@el...>]

On Wed, 2005-07-06 at 00:41 +0300, Antti M V=C3=A4h=C3=A4kotam=C3=A4ki wrot=
e:
> Hmm.. Could we just check if the singleton object already exists in the=20
> memory and not initialize it twice?

Sounds reasonable to me.  Or you can put this stuff in a module that
gets used by startup.pl.

> At least for me it is a huge difference that I don't have to watch the=20
> mod_perl apache to start (which takes quite some time) and issue my=20
> request after it has finished - I can just issue the request and it is=20
> executed instantly when the initialization is completed.

But... they do the same thing.  I don't see how the FastCGI one can
actually be ready more quickly, unless it's just the bug you referred to
with reloading during startup.

> Yes, it is just a fork and the forking is really cheap but there is no=20
> way to prevent mod_perl from polluting also much of the static data=20
> shared with the parent process according to this:
>=20
> http://perl.apache.org/docs/1.0/guide/performance.html#toc_Sharing_Memory

I'm one of the maintainers of that page. :)

A noticeable hit on the first request is more likely to be due to making
a database connection or reopening log files than overhead from copying
dirty pages.

> By default, no it doesn't. It's just a single Perl interpreter serving=20
> requests one by one.

Then you can get the same effect in mod_perl by setting the process
controls in httpd.conf to run a single server, or by starting apache
with the -X flag which tells it not to fork.

If it's just for dev though, the oi2_daemon server would probably work
just as well.

- Perrin