From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Timing of 'SELECT 1' |
Date: | 2004-03-10 19:06:38 |
Message-ID: | 404F673E.50207@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
>>There seems to be a 'PostgreSQL ping' time of about 1-2 ms in best case
>>conditions which limits the amount of queries you can fire off in 1
>>second, no matter how simple. In certain rare cases this is something
>>of a bottleneck. In my personal case it would be nice to see that time
>>lower because converted COBOL applications tend to generate a lot of
>>'simple' queries.
>>
>>
>
>Yes, most of that might be network time. I am using log_duration, which
>I think just tests backend time, not network transfer time, but I might
>be wrong. I want to look into this as it seems no one knows the answer.
>
>
>
That's easy to verify with standard ping. In my switched 100MBit
network, roundtrip for small packets is about 0.2 ms, and 0.5ms for 1kb
packets. How about context switch latency?
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-10 19:18:17 | Re: Timing of 'SELECT 1' |
Previous Message | Tom Lane | 2004-03-10 19:06:00 | Re: [HACKERS] Shouldn't B'1' = 1::bit be true? |