pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Greg Sabino Mullane <greg@turnstep.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: DBD::Pg performance bites compared to DBD::mysql?
Date: 14 Jun 2005 02:44:28 -0400
Message-ID: <87u0k11lpv.fsf@stark.xeocode.com> (raw)
In-Reply-To: <933399e2f40b843429889b52d6ebae8d@biglumber.com>
References: <933399e2f40b843429889b52d6ebae8d@biglumber.com>

"Greg Sabino Mullane" <greg@turnstep.com> writes:

> I still maintain the original test is brain-dead, however. :) It was
> testing for "insert speed" by basically doing this:
> 
> for (1..1000) {
>         $dbh->do("INSERT INTO testtable(a,b) VALUES (1,2)");
> }
> 
> It's as if the people who wrote it *cough*mysql*cough* never heard
> of prepare/execute and did not read the DBI docs.


Sure but wouldn't that show up as more time spent in the server in the parser
and planner? I thought Tom was complaining that it was spending too much time
in the client not waiting on server responses.

I wonder if Postgres is being bitten by doing lots of extra round trips. Maybe
the MySQL driver detects when there are no placeholders and no parameters and
uses a different protocol method that only requires a single round trip? Or
given your example maybe it even notices no result is needed and doesn't even
wait for a response?

-- 
greg




view thread (9+ messages)  latest in thread

Message-ID: <87u0k11lpv.fsf@stark.xeocode.com>
Permalink:  ../87u0k11lpv.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87u0k11lpv.fsf@stark.xeocode.com

 · 

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: gsstark@mit.edu, greg@turnstep.com
  Subject: Re: DBD::Pg performance bites compared to DBD::mysql?
  In-Reply-To: <87u0k11lpv.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