| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Avi Vallarapu <avi(dot)vallarapu(at)percona(dot)com> |
| Cc: | Raghavendra Rao J S V <raghavendrajsv(at)gmail(dot)com>, Avinash Kumar <avinash(dot)vallarapu(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: "checkpointer process" is consuming more memory. How to control it? |
| Date: | 2018-08-23 13:46:28 |
| Message-ID: | 20180823134628.yax2zzcklcmsk36w@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2018-08-22 11:14:48 -0300, Avi Vallarapu wrote:
> Seams like you are with the default or fairly less checkpoint_* settings.
>
> You need to look at several patterns to understand the best values for
> these settings.
>
> For now, i can say 300 seconds for checkpoint_timeout could be fairly very
> less. Try increasing that with a reload.
>
> See this =>
> https://www.percona.com/blog/2018/06/15/tuning-postgresql-for-sysbench-tpcc/
>
> Please do note that delaying checkpointing could also increase the time for
> crash recovery/shutdown, etc.........
This seems to have not that much to do with the problem the OP has, no?
I suggest just using pmap -d $process_id_of_checkpointer
that'll likely show that it doesn't actually use much memory, but that
the RSS originates from the shared memory it has touched.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-08-23 14:07:45 | Re: MultiXactId 24018 has not been created yet -- apparent wraparound error |
| Previous Message | Adrian Klaver | 2018-08-23 13:04:29 | Re: pg_sample |