some flawed benchmarks

2008-07-09 Thread adam . prime
A couple of months ago i was going through slides from gozers "From CGI to mod_perl 2.0, Fast!" talk, which has some benchmarks comparing CGI, perlrun and registry to each other. At which point i realized that i've never really known how much faster using straight handlers is than using on

Re: some flawed benchmarks

2008-07-10 Thread Dodger
I appreciate this, as I'd been wondering. But it also prompts me to.. I gotta ask... No offence but... Don't you know what a here_doc is? -- Dodger 2008/7/9 <[EMAIL PROTECTED]>: > A couple of months ago i was going through slides from gozers "From CGI to > mod_perl 2.0, Fast!" talk, which has

Re: some flawed benchmarks

2008-07-10 Thread Dodger
Oh. I would also recommend three variants, based on what people often do, what people sometimes do, and what people probably should do when using CGI.pm, which can make a difference (just for thoroughness): Usually done: #!/usr/bin/perl use CGI; print header; print <<"EOF"; Environment du

Re: some flawed benchmarks

2008-07-10 Thread Andy Armstrong
On 10 Jul 2008, at 06:28, [EMAIL PROTECTED] wrote: I'm not sure how well you can really compare the CGI emulation numbers to the PerlHandler numbers, but personally i think the 30%ish improvement from perl-script to modperl is pretty amazing. I wouldn't have imagined it would have been that

Re: some flawed benchmarks

2008-07-10 Thread Adam Prime
I deliberately removed CGI from the script because i personally would never use CGI in something written to be run as straight handlers, and it obviously wouldn't make any sense to use CGI in the CGI emulations, and then not use it in the Handler version. Not using heredoc's shouldn't really h

Re: some flawed benchmarks

2008-07-10 Thread Adam Prime
Andy Armstrong wrote: It would be interesting to see how FCGI compares to those numbers. I don't know anything about fastcgi, but i suppose i could look at that also this evening. Adam

Re: some flawed benchmarks

2008-07-10 Thread Perrin Harkins
On Thu, Jul 10, 2008 at 1:28 AM, <[EMAIL PROTECTED]> wrote: > and here's the conf (these tests were all running through a light mod_proxy > front end too) Note that CGI and FastCGI don't need the proxy frontend. > I'm not sure how well you can really compare the CGI emulation numbers to > the Pe

Re: some flawed benchmarks

2008-07-10 Thread adam . prime
Quoting Perrin Harkins <[EMAIL PROTECTED]>: Note that CGI and FastCGI don't need the proxy frontend. The only reason I did it that way was because that's how apache was already set up on my laptop, and i didn't feel like dorking around with it too much. I could certainly change it around

Re: some flawed benchmarks

2008-07-10 Thread adam . prime
i've changed some stuff and added fastcgi to the mix. i've given numbers through the proxy as well as without it for all the mod_perl examples I've modified the scripts so that they producing the same amount of output for each example (except cgi, which adds a content-length header, so

Re: some flawed benchmarks

2008-07-10 Thread Perrin Harkins
On Thu, Jul 10, 2008 at 11:43 PM, <[EMAIL PROTECTED]> wrote: > If anyone's got any ideas about why the proxy is having as significant an > impact as it is, i'd love to tweak it. There are some proxy settings in recent mod_proxy versions (apache 2.2) which you could experiment with. I haven't tri