Message-ID: <44DC4794.2000507@logix-tt.com>
Date: Fri, 11 Aug 2006 11:02:12 +0200
From: Markus Schaber <schabi@logix-tt.com>
Organization: Logical Tracking and Tracing International AG, Switzerland
User-Agent: Thunderbird 1.5.0.4 (X11/20060713)
MIME-Version: 1.0
To: hansell baran <hansellb@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: slow transfer speeds with PostgreSQL
References: <20060803233939.75401.qmail@web30304.mail.mud.yahoo.com>
In-Reply-To: <20060803233939.75401.qmail@web30304.mail.mud.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Hi, Hansell,

hansell baran wrote:

> When we run the following query "SELECT * FROM big_table", we get the
> following resutls:

Just for Curiosity:

Could you try to "COPY big_table TO stdout" from psql[.exe]? (and
possibly redirect the psql output to /dev/null or so?)

> Is there a way to increase the transfer rates?

Which file system do you use?

Could you try to "VACUUM FULL" the tables?

I assume that, for complex queries, you have all the appropriate indices
etc.

Also, I have to admit, that for single-client scenarios and simple,
mostly read-only queries, PostgreSQL tends to be slower than Access and
MySQL.

However, this changes as soon as you have multiple concurrent writing
clients. You should take this into account when benchmarking your
servers (by modelling the appropriate benchmarks), and when deciding
which database to use (by trying to estimate future usage patterns).


HTH,
Markus

-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org