From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Timing of 'SELECT 1' |
Date: | 2004-03-10 16:42:57 |
Message-ID: | 200403101642.i2AGgwQ16126@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Merlin Moncure wrote:
> Bruce Momjian wrote:
> > I am timing small queries, and found that a PREPARE/EXECUTE of "SELECT
> > 1" takes about 1.2ms on my machine. A normal SELECT doesn't take much
> > longer, so I am wondering why a simpler query isn't faster.
> >
> > Looking at log_executor_stats, I see the following. Execute shows
> > nothing taking much time, mostly < .2ms, but the total seems high. I
> > wonder if one of our standard query start/stop functions is taking too
> > long and can be optimized.
>
> 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.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2004-03-10 16:43:10 | Re: About hierarchical_query of Oracle |
Previous Message | Bruce Momjian | 2004-03-10 16:42:12 | Re: Timing of 'SELECT 1' |