Re: Bypassing shared_buffers
От | Thomas Munro |
---|---|
Тема | Re: Bypassing shared_buffers |
Дата | |
Msg-id | CA+hUKGJNsXGjhsoQCKtFs32W6eLH=P7aWPcHqmq_VV4qxr=2KA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Bypassing shared_buffers (Vladimir Churyukin <vladimir@churyukin.com>) |
Ответы |
Re: Bypassing shared_buffers
Re: Bypassing shared_buffers |
Список | pgsql-hackers |
On Thu, Jun 15, 2023 at 1:37 PM Vladimir Churyukin <vladimir@churyukin.com> wrote: > Ok, got it, thanks. > Is there any alternative approach to measuring the performance as if the cache was empty? There are two levels of cache. If you're on Linux you can ask it to drop its caches by writing certain values to /proc/sys/vm/drop_caches. For PostgreSQL's own buffer pool, it would be nice if someone would extend the pg_prewarm extension to have a similar 'unwarm' operation, for testing like that. But one thing you can do is just restart the database cluster, or use pg_prewarm to fill its buffer pool up with other stuff (and thus kick out the stuff you didn't want in there).
В списке pgsql-hackers по дате отправления: