Phoenix.pm: perlcc

[Andrew Johnson]

Scott Walters wrote:

>Hi folks.
>
>I'm trying to squeeze every ounce of performance possible out of my server
>machine, the Apple 7300/180 (the 180 is for 180 mhz). 
>
>I have one script that is getting hit a lot and should respond quickly,
>and supposedly, Perl spends a lot if not most of its time just parsing
>the source code, so I gave perlcc a whirl.
>
>To those not familiar, perlcc lets perl parse the program, than dumps
>the symbol table and opcode tree as a bunch of C datastructures,
>pre initialized, along with the glue needed to link to libperl,
>saving a program from having to parse the .pl file.
>
>                  normal            perlcc binary
>wiki.cgi       .301 + .678          .361 + 1.547
>assemble.cgi   1.607 + 1.191       1.653 + 2.509
>
>Time is user time + system time.
>
>Instead of being faster, a compiled binary is slower.
>  
>
I've heard of other people having that same problem, but I can't 
remember what explanation they came up with.  At least you're not alone, 
though.