Skip site navigation (1) Skip section navigation (2)

Re: Simple query takes a long time on win2K

From: "A(dot) Mous" <a(dot)mous(at)shaw(dot)ca>
To: 'Magnus Hagander' <mha(at)sollentuna(dot)net>,'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 'Richard Huxton' <dev(at)archonet(dot)com>,pgsql-general(at)postgresql(dot)org,"'Joshua D(dot) Drake'" <jd(at)commandprompt(dot)com>,'Lincoln Yeoh' <lyeoh(at)pop(dot)jaring(dot)my>,pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: Simple query takes a long time on win2K
Date: 2005-03-23 19:57:46
Message-ID: 006001c52fe2$9554bc80$6500a8c0@PETER (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers-win32
OK, I've taken the PII 233 that had win2K pro on it, and installed winXP
home.  Reloaded psql 8.0.1 and the database and ran the exact same query.
Recall with win2K it took 4000ms to get the data to the client (about 1500
rows) and on XP it takes 290ms the first time, and about 250ms every time


Seq Scan on foo (cost=0.00..40.72 rows=1472 width=134) (actual
time=0.000..50.000 rows=1472 loops=1)

By the way, this table only has 7 columns...why is the width described as

I've tried installing the QoS packet scheduler with win2K pro and it did
absolutely nothing.  I will now download ethereal and install on one of the
other win2K pro machines that has high latency, however, what exactly am I
looking for?

You know, among the win2K machines that I've tested so far, if the only slow
ones were the pII 233 and the Celeron 400 I could accept the fact that it's
ancient hardware.  But the pIII800 was also dead slow to return the data to
the client app, and this most recent test clearly shows that the OS is the
problem.  Ug.

I'd greatly appreciate any input on this!  Thanks.

-----Original Message-----
From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net] 
Sent: March 23, 2005 12:04 PM
To: Tom Lane; A. Mous
Cc: Richard Huxton; pgsql-general(at)postgresql(dot)org; Joshua D. Drake; Lincoln
Yeoh; pgsql-hackers-win32(at)postgresql(dot)org
Subject: RE: [GENERAL] Simple query takes a long time on win2K

> > The confusing thing for me is that so far, the only 
> consistent pattern 
> > here is that machines running win2k Pro take roughly 4 seconds to 
> > deliver the data to the client, while win XP machines perform much 
> > better (<200ms to deliver recordset).  I've tried installing QoS 
> > packet scheduler on win2K pro machines to no avail.
> I really thought the QoS thing would be it.  Maybe there was 
> some other thing to do, configuration-wise, to make that do 
> its thing properly?
> If you could reproduce this behavior across the network I 
> would tell you to get out a packet analyzer (ethereal or some 
> such) and sniff the traffic to learn more.  Are there any 
> programs that can sniff local TCP traffic on win2k?

Microsoft ships a network monitor with Win2k Server. Otherwise, just get
ethereal, it works perfectly on win2k.


In response to

pgsql-hackers-win32 by date

Next:From: A. MousDate: 2005-03-24 03:49:22
Subject: Re: Simple query takes a long time on win2K
Previous:From: Magnus HaganderDate: 2005-03-23 19:04:12
Subject: Re: Simple query takes a long time on win2K

pgsql-general by date

Next:From: Rick SchumeyerDate: 2005-03-23 20:00:07
Subject: tsearch2 installation question
Previous:From: Scott FrankelDate: 2005-03-23 19:48:46
Subject: Re: inherited table and rules

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group