Re: Simple query takes a long time on win2K

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "A(dot) Mous" <a(dot)mous(at)shaw(dot)ca>
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:04:12
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE6C713F@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers-win32

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

//Magnus

Responses

Browse pgsql-general by date

  From Date Subject
Next Message elein 2005-03-23 19:38:21 debug_print_plan
Previous Message Andrus 2005-03-23 18:47:36 Re: Using sequence name depending on other column

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message A. Mous 2005-03-23 19:57:46 Re: Simple query takes a long time on win2K
Previous Message Tom Lane 2005-03-23 18:11:18 Re: Simple query takes a long time on win2K