Re: Interesting incosistent query timing - Mailing list pgsql-performance

From Tom Lane
Subject Re: Interesting incosistent query timing
Date
Msg-id 17950.1055895138@sss.pgh.pa.us
Whole thread Raw
In response to Re: Interesting incosistent query timing  (Ernest E Vogelsinger <ernest@vogelsinger.at>)
List pgsql-performance
Ernest E Vogelsinger <ernest@vogelsinger.at> writes:
> I came to the same conclusion - I installed a cron script that performs a
> select against that index on a regular basis (3 minutes). After that even
> the most complex queries against this huge table go like whoosssshhh ;-)
> Would be interesting what one could do to _not_ have to take this basically
> clumsy approach...

Seems like your kernel is falling down on the job: if those files are
the most heavily used ones on the machine, it should be keeping them in
disk cache without such prompting.

If they are not all that heavily used, then you are basically slowing
everything else down in order to speed up these queries (because you're
starving everything else for disk cache).  Which may be a reasonable
tradeoff in your situation, but be aware of what you're doing.

The best compromise may be to buy more RAM ;-)

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres Connections Requiring Large Amounts of Memory
Next
From: "SZŰCS Gábor"
Date:
Subject: Re: Postgres Connections Requiring Large Amounts of Memory