Re: ??: postgres cpu 100% need help

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: "657985552(at)qq(dot)com" <657985552(at)qq(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: ??: postgres cpu 100% need help
Date: 2015-11-23 15:30:15
Message-ID: CACjxUsPg+TEGoxDba0EV4B=BE1agNP2JmGwuO9MnocKa_+CR_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Nov 23, 2015 at 12:20 AM, 657985552(at)qq(dot)com <657985552(at)qq(dot)com> wrote:

> [root(at)pg1 ~]# cat /sys/kernel/mm/transparent_hugepage/enabled
> [always] madvise never
> [root(at)pg1 ~]# cat /sys/kernel/mm/transparent_hugepage/defrag
> [always] madvise never

There's your problem. You need to set those to "never". You can
get immediate relief by echoing 'never' to those pseudo-files, but
you need to configure your system to set them at OS boot time, too.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim Nasby 2015-11-23 16:19:29 Re: Problems with pg_upgrade after change of unix user running db.
Previous Message Melvin Davidson 2015-11-23 13:46:53 Re: current_query='IDLE" in pg_stat_activity