From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: SELECT's take a long time compared to other DBMS |
Date: | 2003-09-04 03:24:19 |
Message-ID: | m33cfd6xss.fsf@chvatal.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
In the last exciting episode, "Relaxin" <me(at)yourhouse(dot)com> wrote:
> All queries were ran on the SERVER for all of the databases I tested.
Queries obviously run "on the server." That's kind of the point of
the database system being a "client/server" system.
The question is what client program(s) you used to process the result
sets. I'd be surprised to see any client process 100K records in any
meaningful way in much less than 30 seconds. Rendering that much data
into a console will take some time. Drawing it into cells on a GUI
window will take a lot more time.
Supposing you were using a graphical client, it would be unsurprising
for it to have submitted something equivalent to "limit 30 rows" (or
whatever you can display on screen), and defer further processing 'til
later. If that were the case, then 26s to process the whole thing
would be a lot more efficient than 5-6s to process a mere 30 rows...
> This is all resulting data for all of the databases that I tested.
You seem to have omitted "all resulting data."
--
If this was helpful, <http://svcs.affero.net/rm.php?r=cbbrowne> rate me
http://www.ntlug.org/~cbbrowne/sap.html
"Women who seek to be equal to men lack ambition. "
-- Timothy Leary
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-09-04 03:36:36 | Re: PostgreSQL Reliability when fsync = false on Linux-XFS |
Previous Message | Christopher Browne | 2003-09-04 03:19:22 | Re: SELECT's take a long time compared to other DBMS |