From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: DBD::Pg performance bites compared to DBD::mysql? |
Date: | 2005-06-05 02:27:55 |
Message-ID: | 87ekbhk05w.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)gborg(dot)postgresql(dot)org
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-05 04:40:43 | Re: DBD::Pg performance bites compared to DBD::mysql? |
Previous Message | Tom Lane | 2005-06-04 14:57:42 | Re: libpq, PQExecParams and the inserting of binary data |