From: | "Greg Quinn" <greg(at)officium(dot)co(dot)za> |
---|---|
To: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Slow performance on Windows .NET and OleDb |
Date: | 2006-03-29 11:00:20 |
Message-ID: | 000f01c6531f$fcbc0570$0200a8c0@pta.homex.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> how many rows does it return ? a few, or a lot ?
3000 Rows - 7 seconds - very slow
Which client library may have a problem? I am using OleDb, though haven't
tried the .NET connector yet.
Network configuration?? I am running it off my home PC with no network. It
is P4 2.4 with 1 Gig Ram. Windows XP
----- Original Message -----
From: "PFC" <lists(at)peufeu(dot)com>
To: "Greg Quinn" <greg(at)officium(dot)co(dot)za>
Sent: Wednesday, March 29, 2006 11:02 AM
Subject: Re: [PERFORM] Slow performance on Windows .NET and OleDb
>
>> select * from users
>> which returns 4 varchar fields, there is no where clause
>
> how many rows does it return ? a few, or a lot ?
>
>> Yes, I am running the default postgres config. Basically I have been a
>> MySQL user and thought I would like to check out PostGreSql.
>
> Good idea...
>
> From the tests I made, on simple queries like yours, with no joins, speed
> pf pg 8.x is about the same as mysql 5.x ; that is to say very fast. If
> you have a performance problem on something so basic, and moreover on
> windows, it smells like a problem in the client library, or in the TCP
> transport between client and server.
> I remember messages saying postgres on windows was slow some time ago
> here, and it turned out to be a problem in the network configuration of
> the machine.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2006-03-29 11:21:15 | Re: Slow performance on Windows .NET and OleDb |
Previous Message | Theo Kramer | 2006-03-29 10:52:31 | Re: Indexes with descending date columns |