Re: DBD::Pg performance bites compared to DBD::mysql? - Mailing list pgsql-interfaces

From Greg Stark
Subject Re: DBD::Pg performance bites compared to DBD::mysql?
Date
Msg-id 87ekbhk05w.fsf@stark.xeocode.com
Whole thread Raw
In response to DBD::Pg performance bites compared to DBD::mysql?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: DBD::Pg performance bites compared to DBD::mysql?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: DBD::Pg performance bites compared to DBD::mysql?  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-interfaces
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



pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq, PQExecParams and the inserting of binary data
Next
From: Tom Lane
Date:
Subject: Re: DBD::Pg performance bites compared to DBD::mysql?