From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Speeding up JSON + TSQUERY + GIN |
Date: | 2017-02-27 18:22:25 |
Message-ID: | CAMkU=1xyf5ypGew=cgFuczQHqtc59J1CTf2EugF0hwSWu65ZCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sun, Feb 26, 2017 at 5:28 AM, Sven R. Kunze <srkunze(at)mail(dot)de> wrote:
>
>
> Using "select pg_prewarm('docs');" and on any of the indexes doesn't help
> either.
> After a "systemctl stop postgresql.service && sync && echo 3 >
> /proc/sys/vm/drop_caches && systemctl start postgresql.service" the age=20,
> 30 or name=john queries are slow again.
>
>
> Is there a way to speed up or to warm up things permanently?
>
If by 'permanently', you mean even when you intentionally break things,
then no. You will always be able to intentionally break things. There is
on-going discussion of an auto-prewarm feature. But that doesn't yet
exist; and once it does, a super user will always be able to break it.
Presumably you have a use-case in mind other than intentional sabotage of
your caches by root. But, what is it? If you reboot the server
frequently, maybe you can just throw 'select pg_prewarm...' into an init
script?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Sven R. Kunze | 2017-02-28 08:27:09 | Re: Speeding up JSON + TSQUERY + GIN |
Previous Message | Sven R. Kunze | 2017-02-27 14:46:59 | Re: Speeding up JSON + TSQUERY + GIN |