From: | "A(dot) Mous" <a(dot)mous(at)shaw(dot)ca> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Simple query takes a long time on win2K |
Date: | 2005-03-23 09:57:09 |
Message-ID: | 000001c52f8e$adaa7c60$6500a8c0@PETER |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers-win32 |
Hi,
I have a table with about 1500 records. My query is very basic: SELECT *
FROM foo;
With postgres 8.0.1 on Win XP (Celeron 2400, 500MB RAM) it returns the
results in about 80ms. The same query on the same database, tested on three
different win2k machines all running 8.0.1, takes roughly 4 seconds. Win2K
machines are as follows:
1) PIII 800, 256MB RAM
2) Celeron 400, 128MB RAM
3) PII 233, 128MB RAM
All machines are currently using the default settings upon install. I've
tried adjusting shared_buffers and work_mem but nothing seems to make any
difference.
EXPLAIN ANALYZE on WinXP machine gives:
Seq Scan on foo (cost=0.00..65.71 rows=1471 width=95) (actual
time=0.000..0.000 rows=1472 loops=1)
Same on #3 Win2K machine gives:
Seq Scan on foo (cost=0.00..40.72 rows=1472 width=95) (actual
time=0.000..80.000 rows=1472 loops=1)
All queries are executed locally on the server. Can anyone please explain
the profound performance difference here (which appear to be related to the
OS)?
Much thanks in advance!
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2005-03-23 10:18:57 | Re: Using sequence name depending on other column |
Previous Message | Marco Colombo | 2005-03-23 09:50:09 | Re: multi line text data/query ?bug? |
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-03-23 11:29:21 | Re: Simple query takes a long time on win2K |
Previous Message | Magnus Hagander | 2005-03-21 08:49:05 | Re: explain analyze timings |