| From: | Stefan Keller <sfkeller(at)gmail(dot)com> |
|---|---|
| To: | Andy Colson <andy(at)squeakycode(dot)net> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? |
| Date: | 2012-02-26 20:37:45 |
| Message-ID: | CAFcOn28oCqoNJFVL8wdc6+QcMNuzLC5YuoamCJGF5npe8JT+WA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
2012/2/26 Andy Colson <andy(at)squeakycode(dot)net> wrote:
>>> How about after you load the data, vacuum freeze it, then do something
>>> like:
>>>
>>> SELECT count(*) FROM osm_point WHERE tags @> 'tourism=>junk'
>>>
>>> -Andy
>>
>>
>> That good idea is what I proposed elsewhere on one of the PG lists and
>> got told that this does'nt help.
>>
...
> I don't buy that. Did you test it? Who/where did you hear this? And...
> how long does it take after you replace the entire table until things are
> good and cached? One or two queries?
>
> After a complete reload of the data, do you vacuum freeze it?
Yes.
> After a complete reload of the data, how long until its fast?
Just after the second query. You can try it yourself online here:
http://bit.ly/A8duyB
-Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Keller | 2012-02-26 20:56:35 | Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? |
| Previous Message | Cédric Villemain | 2012-02-26 19:36:19 | Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? |