Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection; - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Date
Msg-id 492058E2.8060201@dunslane.net
Whole thread Raw
In response to Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
List pgsql-hackers

Tom Lane wrote:
> I wrote:
>   
>> On my Fedora 9 machine, the overhead to start plperl seems to be about
>> 40 msec.  This compares unfavorably to the time to start perl from the
>> command line, which is under 4 msec.  I see that /usr/bin/perl pulls in
>> libperl.so, so it's paying the same shlib overhead as we do.  How is it
>> that we take ten times longer to start up?
>>     
>
> The above number was for plperl in a SQL_ASCII database.
> Some more data points:
>
>         plperl        plperlu
>
> SQL_ASCII    40        18
> UTF8        67        18
>
> which leads to the conclusion that those random little startup things
> plperl does are just unbelievably expensive.
>
>             
>   

I suspect much of this time is taken in loading perl modules, (strict, 
Safe, utf8, SPI among others), not in anything very special that we do.:
   andrew@constanza plperl]$ time perl -e ';'
   real    0m0.004s   user    0m0.003s   sys     0m0.001s   [andrew@constanza plperl]$ time perl -e 'use strict; use
Safe;useutf8;'
 
   real    0m0.053s   user    0m0.016s   sys     0m0.007s

cheers

andrew






pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: Enable script to generate preproc.y in build process.
Next
From: "Jaime Casanova"
Date:
Subject: Re: CVS can't be built on mingw