| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: DBD::Pg performance bites compared to DBD::mysql? |
| Date: | 2005-08-22 01:25:56 |
| Message-ID: | 5495.1124673956@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
"Greg Sabino Mullane" <greg(at)turnstep(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2005-08-22 01:47:27 | Re: DBD::Pg performance bites compared to DBD::mysql? |
| Previous Message | Greg Sabino Mullane | 2005-08-22 00:20:00 | Re: DBD::Pg performance bites compared to DBD::mysql? |