From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: DBD::Pg performance bites compared to DBD::mysql?
Date: 04 Jun 2005 22:27:55 -0400
Message-ID: <87ekbhk05w.fsf@stark.xeocode.com> (raw)
In-Reply-To: <1015.1117775836@sss.pgh.pa.us>
References: <1015.1117775836@sss.pgh.pa.us>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> I'm not any kind of Perl module guru, but it looks to me like the
> explanation for the discrepancy is that much of DBD::mysql is written
> in C while the equivalent code in DBD::Pg is written in Perl. This is
> killing us for any app written in Perl :-( --- the above trace only
> shows a factor of 2 total penalty, but I've seen up to a factor of 4 in
> other cases. There is no way that a client-side driver should be taking
> several times longer than the backend to process a SQL command :-(
What version of DBD::Pg did you test with? Development was pretty moribund for
a while but has picked up recently, just in time for 8.0 and the new binary
prepared query support.
Incidentally, the DBD::Pg mailing list is dbdpg-general@gborg.postgresql.org
--
greg
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: gsstark@mit.edu, tgl@sss.pgh.pa.us
Subject: Re: DBD::Pg performance bites compared to DBD::mysql?
In-Reply-To: <87ekbhk05w.fsf@stark.xeocode.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