From: Scott Marlowe <smarlowe@qwest.net>
To: Joost Kraaijeveld <J.Kraaijeveld@Askesis.nl>
Cc: pgsql-performance@postgresql.org
Subject: Re: What kind of performace can I expect and how to
Date: Mon, 02 Aug 2004 10:11:46 -0600
Message-ID: <1091463106.27166.33.camel@localhost.localdomain> (raw)
In-Reply-To: <A3D1526C98B7C1409A687E0943EAC41001EA5A@obelix.askesis.nl>
References: <A3D1526C98B7C1409A687E0943EAC41001EA5A@obelix.askesis.nl>
On Mon, 2004-08-02 at 06:21, Joost Kraaijeveld wrote:
> Hi all,
>
> My system is a PostgreSQL 7.4.1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 20020903 (Red Hat Linux 8.0 3.2-7). It has a Pentium III-733 Mhz with 512 MB ram. It is connected to my workststation (dual XEON 1700 with 1 Gb RAM) with a 100 Mb switched network.
>
> I have a table with 31 columns, all fixed size datatypes. It contains 88393 rows. Doing a "select * from table" with PGAdmin III in it's SQL window, it takes a total of 9206 ms query runtime an a 40638 ms data retrievel runtime.
This means it took the backend about 9 seconds to prepare the data, and
40 or so seconds total (including the 9 I believe) for the client to
retrieve and then display it.
> Is this a reasonable time to get 88393 rows from the database?
Depends on your row size really. I'm certain you're not CPU bound if
you've only got one hard drive. Put that data on a 20 way RAID5 array
and I'm sure it would come back a little quicker.
> If not, what can I do to find the bottleneck (and eventually make it faster)?
The bottleneck is almost always IO to start with. First, as another
drive and mirror it. Then go to RAID 1+0, then add more and more
drives.
Read this document about performance tuning:
http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
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: smarlowe@qwest.net, J.Kraaijeveld@Askesis.nl
Subject: Re: What kind of performace can I expect and how to
In-Reply-To: <1091463106.27166.33.camel@localhost.localdomain>
* 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