From: Jakob Oestergaard <jakob@unthought.net>
To: "Stephan T. Lavavej" <stl@nuwen.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Process Creation Speed
Date: Thu, 22 Apr 2004 15:40:43 +0200 [thread overview]
Message-ID: <20040422134043.GL30687@unthought.net> (raw)
In-Reply-To: <200404191245.i3JCjqal006292@localhost.localdomain>
On Mon, Apr 19, 2004 at 05:44:12AM -0700, Stephan T. Lavavej wrote:
> Thanks to all who have responded.
>
...
>
> I am writing a web-based forum entirely in C++, rejecting interpreted
> languages (Perl, PHP, ASP, etc.) and relational databases (MySQL,
> PostGreSQL, etc.) entirely. My forum consists of "kiddy" CGI processes
> which talk over the network to a persistent "mommy" daemon who keeps all
> forum state in main memory.
You could consider loading your .o as an apache module, rather than
executing it as a CGI program.
I was involved in one project where we did this with good success. Even
segfaults in our module would "only" take down one of the Apache
sub-processes, so while they incur performance overhead (and of course
should be fixed no matter what - which luckily is very easy (using for
example { if (!fork()) abort(); } to create snapshot coredumps)), it's
not catastrophic. It's entirely realistic to write a good module for
Apache in a fairly short timespan.
/ jakob
next prev parent reply other threads:[~2004-04-22 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 2:16 Process Creation Speed Stephan T. Lavavej
2004-04-18 5:44 ` Eric
2004-04-19 0:30 ` Jamie Lokier
2004-04-19 2:15 ` Eric
2004-04-19 3:04 ` Jamie Lokier
2004-04-19 5:43 ` Eric
2004-04-19 9:48 ` Jamie Lokier
2004-04-19 12:09 ` Johannes Stezenbach
2004-04-19 12:44 ` Stephan T. Lavavej
2004-04-19 22:48 ` David Lang
2004-04-22 13:40 ` Jakob Oestergaard [this message]
2004-04-19 13:28 ` Jamie Lokier
[not found] <1MFUQ-1zo-3@gated-at.bofh.it>
[not found] ` <1MGnU-1U9-19@gated-at.bofh.it>
2004-04-19 15:43 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040422134043.GL30687@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stl@nuwen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox