Re: BUG #14345: run multi-PG9.6 on One Host, hang when checkpoint

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: digoal(at)126(dot)com
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14345: run multi-PG9.6 on One Host, hang when checkpoint
Date: 2016-09-29 14:48:19
Message-ID: CACjxUsPMjty6z5-Vrd9b4Rn9ULpxAiH_bkw-2GmbQg0C_iNYfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 29, 2016 at 12:35 AM, <digoal(at)126(dot)com> wrote:

> encountered the problem of Hang checkpoint.

> vm.overcommit_ratio = 90
> vm.swappiness = 0

If you change vm.swappiness to 10 can you still see the problem?

The reason I ask is that vm.overcommit_ratio sets the maximum RAM
that can be allocated to swap size plus the specified percentage of
actual RAM (in your case 90% of RAM in addition to allocated swap
space). On the other hand, depending on kernel version,
vm.swappiness = 0 may be telling the OS not to swap anything out,
even if it is never accessed (i.e., it should prefer to throw away
even a very recently referenced page in the cache). This
combination of settings seems somewhat likely to cause problems.

While "conventional wisdom" is that setting vm.swappiness = 0
improves performance, the few benchmarks I have seen related to
that show otherwise.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2016-09-29 15:30:53 Re: BUG #14344: string_agg(DISTINCT ..) crash
Previous Message huang 2016-09-29 14:48:14 Re: vacuumdb parallel has a deadlock detected in 9.5.4