| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "A(dot) 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(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 18:11:18 |
| Message-ID: | 8594.1111601478@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers-win32 |
"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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-23 18:36:33 | Re: [GENERAL] contrib module intagg crashing the backend |
| PostgreSQL : Re : | A. Mous | 2005-03-23 18:05:16 | PostgreSQL : Re : 간단한 쿼리는 윈 토토에서 오랜 시간이 걸립니다 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-03-23 19:04:12 | Re: Simple query takes a long time on win2K |
| PostgreSQL : Re : | A. Mous | 2005-03-23 18:05:16 | PostgreSQL : Re : 간단한 쿼리는 윈 토토에서 오랜 시간이 걸립니다 |