From: | "A(dot) Mous" <a(dot)mous(at)shaw(dot)ca> |
---|---|
To: | 'Magnus Hagander' <mha(at)sollentuna(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Simple query takes a long time on win2K |
Date: | 2005-03-23 16:37:28 |
Message-ID: | 006301c52fc6$9a391730$6500a8c0@PETER |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
So, does this lend evidence to the theory that the difference is due to
insufficient RAM in all of the win2K pro machines?
-----Original Message-----
From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
Sent: March 23, 2005 9:29 AM
To: A. Mous; pgsql-general(at)postgresql(dot)org
Subject: RE: [GENERAL] Simple query takes a long time on win2K
> You're right, the Celeron 2400 is much faster than the 200,
> but not that much more than the 1800, and all win2k
> (professional) machines are serving up the records in exactly
> the same amount of time.
>
> Across a network (issuing the query from the 2400 celeron win
> XP to the 233 PII win2k) the records are served up in about
> 300ms! Much faster than simply performing the exact same
> query locally on the PII.
>
> Now I'm really confused!
>
> Any ideas?
Yes, I suspect it has to do with context switching. When you run it
remotely the server can do it's job without much interference. When you
run the client on the same machine, it keeps flipping back and forth
between the server and the client.
You might get better performance on Win2k server, as that would increase
the timeslice for each piece of work. Also, try tweaking the
"Performance boost for foreground application" on the performance tab of
the system properties.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | A. Mous | 2005-03-23 16:40:19 | Re: Simple query takes a long time on win2K |
Previous Message | Dawid Kuroczko | 2005-03-23 16:34:49 | Re: Delay INSERT |