pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Carlo Stonebanks <stonec.register@sympatico.ca>
To: pgsql-performance@postgresql.org
Subject: Performance costs of various PL languages
Date: Tue, 27 Dec 2011 16:09:50 -0500
Message-ID: <295DF03C1B134B0BBD05A8F54D985C76@CAPRICA> (raw)
In-Reply-To: <4BFE8F4F0200002500031BA2@gw.wicourts.gov>
References: <hsv49v$312j$1@news.hub.org>
	<4BFE8F4F0200002500031BA2@gw.wicourts.gov>

We are currently using pltclu as our PL of choice AFTER plpgSql.

I'd like to know if anyone can comment on the performance costs of the
various PL languages BESIDES C. For example, does pltclu instantiate faster
than pltcl (presumably because it uses a shared interpreter?) Is Perl more
lightweight?

I know that everything depends on context - what you are doing with it, e.g.
choose Tcl for string handling vs. Perl for number crunching - but for those
who know about this, is there a clear performance advantage for any of the
various PL languages - and if so, is it a difference so big to be worth
switching?

I ask this because I had expected to see pl/pgsql as a clear winner in terms
of performance over pltclu, but my initial test showed the opposite. I know
this may be an apples vs oranges problem and I will test further, but if
anyone has any advice or insight, I would appreciate it so I can tailor my
tests accordingly.


Thanks,

Carlo






view thread (5+ messages)  latest in thread

Message-ID: <295DF03C1B134B0BBD05A8F54D985C76@CAPRICA>
Permalink:  ../295DF03C1B134B0BBD05A8F54D985C76@CAPRICA/
Also on:    postgresql.org/message-id/295DF03C1B134B0BBD05A8F54D985C76@CAPRICA

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: stonec.register@sympatico.ca
  Subject: Re: Performance costs of various PL languages
  In-Reply-To: <295DF03C1B134B0BBD05A8F54D985C76@CAPRICA>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox