Re: Postgres performance comments from a MySQL user

At 22:10 13.06.2003, scott.marlowe said:
--------------------[snip]--------------------
>Good idea. Don't forget to make sure it sets effective_cache_size while
>we're at it. Just add up the kernel cache size and the free memory on a
>machine to get an approximation.
--------------------[snip]--------------------

Scott - while we're at it, a quick question.

On that machine, cat /proc/meminfo reports "Cached: 1740844 kB" (which is
approx. 1.6GB cache), the machine has 1GB memory installed. So I did what
you suggested before:
# 1.6GB ~= 200000 pages at 8k
effective_cache_size = 200000

I have a query that runs for 17secs for the first time. Now, when executed
a second time, it consumes 270 msec. From the third execution it's running
with 29 msec.

However this only holds for the open connection. When connecting anew, it
starts with 270 msec and drops to 29 msec again.

Any clues about this interesting behaviour?

--
>O Ernest E. Vogelsinger
(\) ICQ #13394035
^ http://www.vogelsinger.at/