pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vince Lasmarias <vincent.lasmarias@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: High CPU load when 'free -m' shows low 'free' memory even though large 'cached' memory still available
Date: Thu, 05 Jun 2014 09:47:37 -0400
Message-ID: <6015.1401976057@sss.pgh.pa.us> (raw)
In-Reply-To: <CABnAvF3ii0gGds19W4LKK4US+gmshYzv-jhH6XYds12F9172-Q@mail.gmail.com>
References: <CABnAvF3ii0gGds19W4LKK4US+gmshYzv-jhH6XYds12F9172-Q@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>

Vince Lasmarias <vincent.lasmarias@gmail.com> writes:
> For the past few days, we've been seeing unexpected high CPU spikes in our
> system.

Recent reports have suggested that disabling transparent huge page
management in your kernel can help with this.  If the excess CPU
load is mostly "system" time not "user" time then this is probably
the culprit.

			regards, tom lane


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (3+ messages)  latest in thread

Message-ID: <6015.1401976057@sss.pgh.pa.us>
Permalink:  ../6015.1401976057@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6015.1401976057@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, vincent.lasmarias@gmail.com
  Subject: Re: High CPU load when 'free -m' shows low 'free' memory even though large 'cached' memory still available
  In-Reply-To: <6015.1401976057@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox