pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Sabino Mullane <greg@turnstep.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: DBD::Pg performance bites compared to DBD::mysql?
Date: Sun, 21 Aug 2005 21:25:56 -0400
Message-ID: <5495.1124673956@sss.pgh.pa.us> (raw)
In-Reply-To: <e8701beb659e7207431e08c37b69bcaf@biglumber.com>
References: <e8701beb659e7207431e08c37b69bcaf@biglumber.com>

"Greg Sabino Mullane" <greg@turnstep.com> writes:
> I can't imagine that it was causing a factor of 2 difference, but I've
> changed the code in DBD::Pg to make do() a lot smarter, for brain-dead
> benchmarks such as MySQL's that use do() instead of prepare/execute
> like they should. In short, DBD::Pg will short-circuit a lot of the usual
> work and call PQexec directly if it can get away with it, which should
> make the profile Tom posted look a lot better. It also avoids overhead of
> going through Pg.pm, and is all C/XS code now. Hopefully, this should
> make the benchmarking results a little more fair. :) This is now in
> cvs, and will be part of the upcoming version 1.44 of DBD::Pg.

Cool.  Thanks for doing that.  Do you have an idea when 1.44 will
be out?

			regards, tom lane



view thread (9+ messages)  latest in thread

Message-ID: <5495.1124673956@sss.pgh.pa.us>
Permalink:  ../5495.1124673956@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/5495.1124673956@sss.pgh.pa.us

 · 

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-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, greg@turnstep.com
  Subject: Re: DBD::Pg performance bites compared to DBD::mysql?
  In-Reply-To: <5495.1124673956@sss.pgh.pa.us>

* 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