pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Relaxin <noname@spam.com>
To: pgsql-performance@postgresql.org
Subject: Re: SELECT's take a long time compared to other DBMS
Date: Thu, 4 Sep 2003 07:35:24 -0700
Message-ID: <bj7iip$205k$1@news.hub.org> (raw)
References: <bj611t$1o2g$1@news.hub.org>
	<1062673303.5200.135.camel@fuji.krosing.net>

So after you did that, where able to position to ANY record within the
resultset?

Ex. Position 100,000; then  to Position 5; then to position 50,000, etc...

If you are able to do that and have your positioned row available to you
immediately, then I'll believe that it's the ODBC driver.

"Hannu Krosing" <hannu@tm.ee> wrote in message
news:1062673303.5200.135.camel@fuji.krosing.net...
> Relaxin kirjutas N, 04.09.2003 kell 03:28:
> > I have a table with 102,384 records in it, each record is 934 bytes.
>
> I created a test database on my Linux (RH9) laptop with 30GB/4200RPM ide
> drive and P3-1133Mhz, 768MB, populated it with 128000 rows of 930 bytes
> each and did
>
> [hannu@fuji hannu]$ time psql test100k -c 'select * from test' >
> /dev/null
>
> real    0m3.970s
> user    0m0.980s
> sys     0m0.570s
>
> so it seems definitely not a problem with postgres as such, but perhaps
> with Cygwin and/or ODBC driver
>
> I also ran the same query  using the "standard" pg adapter:
>
> >>> import pg, time
> >>>
> >>> con = pg.connect('test100k')
> >>>
> >>> def getall():
> ...     t1 = time.time()
> ...     res = con.query('select * from test')
> ...     t2 = time.time()
> ...     list = res.getresult()
> ...     t3 = time.time()
> ...     print t2 - t1, t3-t2
> ...
> >>> getall()
> 3.27637195587 1.10105705261
> >>> getall()
> 3.07413101196 0.996125936508
> >>> getall()
> 3.03377199173 1.07322502136
>
> which gave similar results
>
> ------------------------------
> Hannu
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html
>





view thread (34+ messages)  latest in thread

Message-ID: <bj7iip$205k$1@news.hub.org>
Permalink:  ../bj7iip$205k$1@news.hub.org/
Also on:    postgresql.org/message-id/bj7iip$205k$1@news.hub.org

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: noname@spam.com
  Subject: Re: SELECT's take a long time compared to other DBMS
  In-Reply-To: <bj7iip$205k$1@news.hub.org>
  References: <bj611t$1o2g$1@news.hub.org> <1062673303.5200.135.camel@fuji.krosing.net> <bj7iip$205k$1@news.hub.org>

* 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