Re: Slow performance on Windows .NET and OleDb

From: PFC
Subject: Re: Slow performance on Windows .NET and OleDb
Date: ,
Msg-id: op.s66aqgokcigqcu@apollo13
(view: Whole thread, Raw)
In response to: Re: Slow performance on Windows .NET and OleDb  ("Greg Quinn")
List: pgsql-performance

Tree view

Slow performance on Windows .NET and OleDb  ("Greg Quinn", )
 Re: Slow performance on Windows .NET and OleDb  ("Merlin Moncure", )
 Re: Slow performance on Windows .NET and OleDb  ("Jim C. Nasby", )
  Re: Slow performance on Windows .NET and OleDb  ("Joshua D. Drake", )
 Re: Slow performance on Windows .NET and OleDb  ("Greg Quinn", )
  Re: Slow performance on Windows .NET and OleDb  (Ruben Rubio Rey, )
   Re: Slow performance on Windows .NET and OleDb  (Chris, )
 Re: Slow performance on Windows .NET and OleDb  ("Greg Quinn", )
  Re: Slow performance on Windows .NET and OleDb  (Markus Schaber, )
 Re: Slow performance on Windows .NET and OleDb  ("Greg Quinn", )
  Re: Slow performance on Windows .NET and OleDb  (PFC, )
  Re: Slow performance on Windows .NET and OleDb  ("Merlin Moncure", )
  Re: Slow performance on Windows .NET and OleDb  (Christopher Kings-Lynne, )
 [Solved] Slow performance on Windows .NET and OleDb  ("Greg Quinn", )
  Re: [Solved] Slow performance on Windows .NET and OleDb  ("Dave Dutcher", )
   Re: [Solved] Slow performance on Windows .NET and OleDb  (Antoine, )
  Re: [Solved] Slow performance on Windows .NET and OleDb  ("Magnus Hagander", )
   Re: [Solved] Slow performance on Windows .NET and OleDb  (Antoine, )
   Re: [Solved] Slow performance on Windows .NET and OleDb  ("Merlin Moncure", )

> 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 ?


pgsql-performance by date:

From: Vivek Khera
Date:
Subject: Re: Decide between Postgresql and Mysql (help of
From: "Eric Lauzon"
Date:
Subject: Database possible corruption , unsolvable mystery