Hi

I was confused

I thought you were saying cgi-bin is faster than plackup, not plack is slow under cgi-bin

I don't see why that would be surprising, "plack" loads a lot of modules (~97 to Moose ~117) thats going to take extra time

Thanks very much for pointing out the possible use of Plack::App::WrapCGI. Unfortunately, if I run your sample script using the vanilla CGI script from my benchmark as the script argument to Plack::App::WrapCGI->new I get no output at all - not even any headers. I think this might be running it as a PSGI application which would then need further Plackage around it to turn it back into CGI? More reading required at this end, I fear.

Wait a minute, you're trying to use wrapcgi to run plack under cgi-bin again?

Um, thats not the purpose of it

The purpose is to run a "vanilla cgi" as a persistent process, not under cgi-bin

Think of plack/wrapcgi like Apache::Registry or ModPerl::Registry for your regular old fashioned cgi-bin scripts

As long as you write them well (as per CGI to mod_perl Porting. mod_perl Coding guidelines, like using CGI::Application or ... ) then they should seamlessly run under mod_perl or plack, and run faster