From: Tatsuhiko Miyagawa <miyagawa@gmail.com>
To: Peter Vereshagin <peter@vereshagin.org>
Cc: Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, Petr Baudis <pasky@suse.cz>,
Eric Wong <normalperson@yhbt.net>,
Sam Vilain <sam.vilain@catalyst.net.nz>,
Juan Jose Comellas <juanjo@comellas.org>,
John Goerzen <jgoerzen@complete.org>
Subject: Re: gitweb, FastCGI and PSGI/Plack
Date: Tue, 11 May 2010 11:56:43 -0700 [thread overview]
Message-ID: <AANLkTinDzAgLckK6z08DJwZPWRmXywQ69EImTaiFsDOE@mail.gmail.com> (raw)
In-Reply-To: <20100511094409.GB5220@screwed.box>
2010/5/11 Peter Vereshagin <peter@vereshagin.org>:
> I know St. Peter won't call your name, Jakub!
> 2010/05/11 11:29:07 +0200 Jakub Narebski <jnareb@gmail.com> => To Tatsuhiko Miyagawa :
>
> JN> gitweb running as FastCGI script (using ab, ApacheBench). Do you know
> JN> any pure-Perl FastCGI server with minimal dependencies, and pure-Perl
>
> I'd like to know about the pure-perl FastCGI protocol implementation either, at
> least to make tests for FCGI::Spawn.
There are two pure perl FCGI protocol implementations (caller side)
available: Net::FastCGI and FCGI::Client.
Plack::App::FCGIDispatcher is a PSGI application to connect to a
FastCGI external daemon over TCP or UNIX sockets, so you can use pure
perl PSGI web servers such as Starman to talk to them. But since it's
all pure perl and experimental and not suited for the benchmarking,
but it could be handy for testing (we actually use FCGI::Client to
test our own FastCGI server side implementation in Plack).
When I seriously want to benchmark FastCGI i always use nginx or
lighttpd, which is easy to install and doesn't need external modules
such as the case with Apache.
--
Tatsuhiko Miyagawa
prev parent reply other threads:[~2010-05-11 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <g2s693254b91005091428ib188cbd1le5ffa90eace741a8@mail.gmail.com>
2010-05-09 23:05 ` gitweb, FastCGI and PSGI/Plack Jakub Narebski
2010-05-10 0:59 ` Tatsuhiko Miyagawa
2010-05-10 16:26 ` Jakub Narebski
2010-05-10 17:14 ` Tatsuhiko Miyagawa
2010-05-10 1:05 ` Tatsuhiko Miyagawa
2010-05-10 10:32 ` Jakub Narebski
2010-05-10 17:03 ` Tatsuhiko Miyagawa
2010-05-10 18:40 ` Jakub Narebski
2010-05-10 18:43 ` Tatsuhiko Miyagawa
2010-05-10 21:10 ` Jakub Narebski
2010-05-11 0:07 ` Tatsuhiko Miyagawa
2010-05-11 9:29 ` Jakub Narebski
2010-05-11 9:44 ` Peter Vereshagin
2010-05-11 18:56 ` Tatsuhiko Miyagawa [this message]
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=AANLkTinDzAgLckK6z08DJwZPWRmXywQ69EImTaiFsDOE@mail.gmail.com \
--to=miyagawa@gmail.com \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.org \
--cc=jnareb@gmail.com \
--cc=juanjo@comellas.org \
--cc=normalperson@yhbt.net \
--cc=pasky@suse.cz \
--cc=peter@vereshagin.org \
--cc=sam.vilain@catalyst.net.nz \
/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;
as well as URLs for NNTP newsgroup(s).