Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Oleg Serov <serovov(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Date: 2008-11-16 16:46:54
Message-ID: 20081116164654.GC25476@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 16, 2008 at 09:15:28AM -0500, Andrew Dunstan wrote:
> Oleg Serov wrote:
> >Hey, you are wrong, compile time is 1 ms, but not 100 ms, it hapens on
> >first plperl function call, it is perl init problem. not function
> >compilation.
> >
>
> Please do NOT top-answer - it makes threads totally unreadable.
>
> Is a one-off cost per connection of 100ms so bothersome?
>
> The alternative would be to start it up when the backend starts, but
> backend startup cost is already high, so that doesn't seem like a win.

If per-connection costs are a problem, then connection pooling usually
helps.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-16 17:00:33 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;
Previous Message Tom Lane 2008-11-16 16:46:24 Re: Pl/Perl function: Speed of the First time executing pl/perl function in connection;