| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alex - <aintokyo(at)hotmail(dot)com> |
| Cc: | scott(dot)marlowe(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PL/Perl Performance Problems |
| Date: | 2009-12-21 03:39:00 |
| Message-ID: | 25812.1261366740@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alex - <aintokyo(at)hotmail(dot)com> writes:
> Tom, Scott, Alvaro,thanks for the hints on this issue. It looks as if one of the EOD maintenance jobs which does a few extensive queries does push data out of memory leading to this behavior.
> Is there a way to permanently cash some tables into memory?
Not as such, and if there were it probably wouldn't be an overall
performance win anyway, because you'd hurt your maintenance tasks.
What you might consider doing is, at the end of the EOD sequence,
run some dummy queries that scan the tables you use normally, causing
them to get swapped back in so the cache is already primed when people
come to work in the morning.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2009-12-21 06:36:49 | Re: Justifying a PG over MySQL approach to a project |
| Previous Message | Oliver Jowett | 2009-12-21 03:30:58 | Re: Cheapest way to poll for notifications? & Driver improvement question re SSL and notify |