pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Adam Palmblad <apalmblad@dataunison.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Dynamically loaded C function performance
Date: Thu, 11 May 2006 17:05:23 -0500
Message-ID: <20060511220523.GT99570@pervasive.com> (raw)
In-Reply-To: <6B5AF6293A289F45826220B17ABE79370D5ED7@BORON.aers.local>
References: <6B5AF6293A289F45826220B17ABE79370D5ED7@BORON.aers.local>

On Fri, May 05, 2006 at 03:47:53PM -0700, Adam Palmblad wrote:
> Hi,
> We've got a C function that we use here and we find that for every
> connection, the first run of the function is much slower than any
> subsequent runs.  ( 50ms compared to 8ms)
> 
> Besides using connection pooling, are there any options to improve
> performance?

In my experience, connection startup takes a heck of a lot longer than
50ms, so why are you worrying about 50ms for the first run of a
function?

BTW, sorry, but I don't know a way to speed this up, either.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (3+ messages)  latest in thread

Message-ID: <20060511220523.GT99570@pervasive.com>
Permalink:  ../20060511220523.GT99570@pervasive.com/
Also on:    postgresql.org/message-id/20060511220523.GT99570@pervasive.com

 · 

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: jnasby@pervasive.com, apalmblad@dataunison.com
  Subject: Re: Dynamically loaded C function performance
  In-Reply-To: <20060511220523.GT99570@pervasive.com>

* 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