Re: [GENERAL] Simple query takes a long time on win2K
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "A. Mous" <a(dot)mous(at)shaw(dot)ca>
- Cc: "'Richard Huxton'" <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org, "'Magnus Hagander'" <mha(at)sollentuna(dot)net>, "'Joshua D. Drake'" <jd(at)commandprompt(dot)com>, "'Lincoln Yeoh'" <lyeoh(at)pop(dot)jaring(dot)my>, pgsql-hackers-win32(at)postgresql(dot)org
- Subject: Re: [GENERAL] Simple query takes a long time on win2K
- Date: Wed, 23 Mar 2005 13:11:18 -0500
- Message-id: <8594(dot)1111601478(at)sss(dot)pgh(dot)pa(dot)us>
"A. Mous" <a(dot)mous(at)shaw(dot)ca> writes:
> 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?
regards, tom lane
PS: I've added pgsql-hackers-win32 to the cc list.
Home |
Main Index |
Thread Index