Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZAlnu-00033z-FV for pgsql-performance@arkaria.postgresql.org; Thu, 02 Jul 2015 21:13:54 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZAlnt-0003lL-KI for pgsql-performance@arkaria.postgresql.org; Thu, 02 Jul 2015 21:13:53 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZAlnr-0003l9-Ug for pgsql-performance@postgresql.org; Thu, 02 Jul 2015 21:13:52 +0000 Received: from nm24-vm5.bullet.mail.ne1.yahoo.com ([98.138.91.246]) by makus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZAlno-0007He-FR for pgsql-performance@postgresql.org; Thu, 02 Jul 2015 21:13:50 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s2048; t=1435871628; bh=yqRXO2l/NaZt/hqZYW8GpCV2m0K/QXg+NmnIBbGBnCw=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=T+oUquwD3KJjaCejVWuo8cuJBjvroklWjlHwnPjHAsYc06bILtPo6b3xig5cRTOwNiMxPcFCJmHfTsX14SPyMA5/MonQK00/LBSIgmFoV4y9fmf49GAWhiocpksO6+HqQRNioh823MY0Nkge2brlncl82LImQVDASo4PDQv/BY/soECl2mC/gkNLaKeNbvtkeyk5NtkBfwLp9QHiCQBAv2OUWeX1iNpewWSpENVyNCxypKwZr53XRYUE7I8AZms3VgJcpyzhJTZDR5ZGWow4fpgNsljqbSHw4iOrsAX55I+rWhWm1yELUZpQ/pi9zW5WTRTt3YVXj1p/d8ppMlCsRw== Received: from [98.138.100.103] by nm24.bullet.mail.ne1.yahoo.com with NNFMP; 02 Jul 2015 21:13:48 -0000 Received: from [98.138.89.168] by tm102.bullet.mail.ne1.yahoo.com with NNFMP; 02 Jul 2015 21:13:47 -0000 Received: from [127.0.0.1] by omp1024.mail.ne1.yahoo.com with NNFMP; 02 Jul 2015 21:13:47 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 187107.80464.bm@omp1024.mail.ne1.yahoo.com X-YMail-OSG: VlmdQksVM1lLU2lcosIUyWjaDsWJ3lLYQoSYbMlTWHAcTXos0JWGnWYF7Nb.DRi yNMsPiHf29MQFxOKeuurJLXErAmCTXHOpX4kAMh4DXazQ6jeTydXkH3f4DBgh37O4kiJw4bDYlUg AKcsYy6sv1RdeLm_VzCkRyW_vmymxfPIIgUt8VoVXa.4G1wuKWf_W0U0Iqpz8koSdDGXHKtxTWlK Z87x_i6GWCw5uXjOf.S6M_.KUSYQA6fn2ZdHCkOxZfuePZFD8mlaWvJ_IyajzQwYTEHUPVhtm2k7 sFt6u5CDTlXa4JdvZRMjJyHJJ3Ts91bXjsLB5P_vfQlHmix3rq5UiV.OijOMyeh2HxKdvhL7cDld 5THkcLT6.J1MXbhWq5cMhRHuTXYDp1VsaDxkCWKDcTLQm.Y8bsQjSx8G5Map_9iw3XA2znxbCEek IRCDSrjegvBaCM5YaJOcU.a02HtY0joYYZIXhtWsFJ0yVPd2CV2ETXvYZDwBSV85SmUR_shR.isv FxC.zQcpO9FKt_4XDXXt8OYIY Received: by 98.138.105.225; Thu, 02 Jul 2015 21:13:47 +0000 Date: Thu, 2 Jul 2015 21:13:47 +0000 (UTC) From: Kevin Grittner Reply-To: Kevin Grittner To: Josh Berkus , eudald_v , "pgsql-performance@postgresql.org" Message-ID: <1850894508.1303488.1435871627463.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <55959207.7020906@agliodbs.com> References: <55959207.7020906@agliodbs.com> Subject: Re: Sudden connection and load average spikes with postgresql 9.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Length: 502 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Josh Berkus wrote: > On 07/02/2015 08:41 AM, eudald_v wrote: >> And this is how it looks like when the spike happens: >> [system CPU staying over 90%] > I think you have a driver, kernel, Linux memory management, or IO > stack issue. In my experience this is usually caused by failure to disable transparent huge page support. The larger shared_buffers is configured, the bigger the problem. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance