From: Arjen van der Meijden <acmmailing@tweakers.net>
To: pgsql-performance@postgresql.org
Subject: Re: mysql to postgresql, performance questions
Date: Thu, 18 Mar 2010 18:08:34 +0100
Message-ID: <4BA25E12.20906@tweakers.net> (raw)
In-Reply-To: <dcc563d11003180850x35398e9dw98c53bd8b2c2cadb@mail.gmail.com>
References: <4BA23936.2030507@gmail.com>
<dcc563d11003180850x35398e9dw98c53bd8b2c2cadb@mail.gmail.com>
On 18-3-2010 16:50 Scott Marlowe wrote:
> It's different because it only takes pgsql 5 milliseconds to run the
> query, and 40 seconds to transfer the data across to your applicaiton,
> which THEN promptly throws it away. If you run it as
>
> MySQL's client lib doesn't transfer over the whole thing. This is
> more about how each db interface is implemented in those languages.
Its the default behavior of both PostgreSQL and MySQL to transfer the
whole resultset over to the client. Or is that different for Ruby's
MySQL-driver? At least in PHP the behavior is similar for both.
And I certainly do hope its 40ms rather than 40s, otherwise it would be
a really bad performing network in either case (15s for mysql) or very
large records (which I doubt).
I'm wondering if a new connection is made between each query. PostgreSQL
is (afaik still is but I haven't compared that recently) a bit slower on
that department than MySQL.
Best regards,
Arjen
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-performance@postgresql.org
Cc: acmmailing@tweakers.net
Subject: Re: mysql to postgresql, performance questions
In-Reply-To: <4BA25E12.20906@tweakers.net>
* 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