From: PFC <lists@peufeu.com>
To: Greg Quinn <greg@officium.co.za>
To: pgsql-performance@postgresql.org
Subject: Re: Slow performance on Windows .NET and OleDb
Date: Wed, 29 Mar 2006 13:40:54 +0200
Message-ID: <op.s66aqgokcigqcu@apollo13> (raw)
In-Reply-To: <000f01c6531f$fcbc0570$0200a8c0@pta.homex.co.za>
References: <000d01c65261$19a3fa40$0200a8c0@pta.homex.co.za>
<20060328173213.GO75181@pervasive.com>
<442977D7.5060508@commandprompt.com>
<006c01c652f9$1ca9c420$0200a8c0@pta.homex.co.za>
<op.s653ebg3cigqcu@apollo13>
<000f01c6531f$fcbc0570$0200a8c0@pta.homex.co.za>
> 3000 Rows - 7 seconds - very slow
On my PC (athlon 64 3000+ running Linux), selecting 3000 rows with 4
columns out of a 29 column table takes about 105 ms, including time to
transfer the results and convert them to native Python objects. It takes
about 85 ms on a test table with only those 4 columns.
There is definitely a problem somewhere on your system.
I'd suggest running this query in an infinite loop. Logically, it should
use 100% processor, with postgres using some percentage (30% here) and
your client using some other percentage (70% here). Is your processor used
to the max ?
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: lists@peufeu.com, greg@officium.co.za
Subject: Re: Slow performance on Windows .NET and OleDb
In-Reply-To: <op.s66aqgokcigqcu@apollo13>
* 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