Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZkXJS-0004fo-NV for pgsql-performance@arkaria.postgresql.org; Fri, 09 Oct 2015 13:02:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZkXJS-0002tL-8y for pgsql-performance@arkaria.postgresql.org; Fri, 09 Oct 2015 13:02:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZkXJQ-0002qc-6P for pgsql-performance@postgresql.org; Fri, 09 Oct 2015 13:02:17 +0000 Received: from nm5.bullet.mail.gq1.yahoo.com ([98.136.218.70]) by magus.postgresql.org with esmtps (TLS1.0:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZkXJL-0000L8-0L for pgsql-performance@postgresql.org; Fri, 09 Oct 2015 13:02:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s2048; t=1444395727; bh=GsTv7sRA7AH0KkxIdqJzsZnwPseVt70ZumwGc/cAXd0=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=t3Ubw6hQwyeheAwaGF3xb/iwEM/01Tkw/4zyKa6t9lDnqXt7r8K6EHXxhw3kL7v0f3CtGdvawPJXHSouEIvWhy67FgDmjRacEds5PYF52KPR/vJ+js2PF8GcMkiUxhpPFpAJx39921mVrdQrIbLnZq+D3tZ4LXKRcOjjwhxzqydomU8AootuKU4SAe2w+WUhDPtR+w7/f752cYGVUKIP8IAWKFLeSB7FlIMdYyzKC51+0ZtijTDdg0ZWdE9wrM4agv10R6sfzxxKvr1ZcNe7EaKCXyeXNh8ir9IiKQum2iSQ5uHrxVISB1T//V43K5JJQceJP9PthpcHH1yEpQZekA== Received: from [216.39.60.181] by nm5.bullet.mail.gq1.yahoo.com with NNFMP; 09 Oct 2015 13:02:07 -0000 Received: from [98.137.12.242] by tm17.bullet.mail.gq1.yahoo.com with NNFMP; 09 Oct 2015 13:02:07 -0000 Received: from [127.0.0.1] by omp1050.mail.gq1.yahoo.com with NNFMP; 09 Oct 2015 13:02:07 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 892790.6257.bm@omp1050.mail.gq1.yahoo.com X-YMail-OSG: cY6BjD4VM1l3a6N21lPh0rf8UxhLwHbjTLISvIF6_TBi0E1Uq2QJgHnPGDhDP08 3sP7UpvcUu5_2dFWXjwFBpYxm1h44Gg2MN4uO5482P1b5io2jA2fxFTgT3.vZOtIxBQMZkWiGqCl WhXQ6YCwu1TiVMszcywQBTzRZi8FoZSK9n4Ip4L4nQ1.DHduX26dHRaj_SwMNQvQis2u7TCavl3F KnIi5v5PmIcHGLsJMIhXM.8oy0yvK3vIrt5WcJuIDiwrsiZWKrHqVIVkWI5cWhZDr25QPcCfWgNk kRN.oT3n989EaSNO9HhnczajQGA7GhGVl3o5oOJH72QL.tCPBBqy5EmDGQd.kNu75cGeZET4qfe0 pIZ9aWQ2kiruDvf8d7EwU6yzAqAB_OedzdtTTEdmRu0Mux5hsVsT013jyetnRpbNn9PnIGMz92dq bDaVrwqCaLu.k0Q42bRv5e5VkmxLca__SifM.QoHNjSRjli.2gODMtShGuuY87FCrZfAi7sGSlQp DD60c8inJ3quX77cheMFhJPT0uf1cfOE- Received: by 216.39.60.209; Fri, 09 Oct 2015 13:02:07 +0000 Date: Fri, 9 Oct 2015 13:01:53 +0000 (UTC) From: Kevin Grittner Reply-To: Kevin Grittner To: ajaykbs , "pgsql-performance@postgresql.org" Message-ID: <24941167.1086518.1444395713314.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <1443864850869-5868480.post@n5.nabble.com> References: <1443864850869-5868480.post@n5.nabble.com> Subject: Re: Re: Multi processor server overloads occationally with system process while running postgresql-9.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Length: 1582 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 On Saturday, October 3, 2015 4:36 AM, ajaykbs wrote: > version: Postgresql-9.4 > Hardware: HP DL980 (8-processor, 80 cores w/o hyper threading, 512GB RAM) > Operating system: Red Hat Enterprise Linux Server release 6.4 (Santiago) > uname -a : Linux host1 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST > 2013 x86_64 x86_64 x86_64 GNU/Linux Single database with separate tablespace > for main-data, pg_xlog and indexes > > I have a database having 770GB size and expected to grow to 2TB within the > next year. The database was running in a 2processor HP DL560 (16 cores) and > as the transactions of the database were found increasing, we have changed > the hardware to DL980 with 8 processors and 512GB RAM. > > Problem It is observed that at some times during moderate load the CPU > usage goes up to 400% and the users are not able to complete the queries in > expected time. But the load is contributed by some system process only. The > average connections are normally 50. But when this happens the connections > will shoot up to max-connections. You might find this thread interesting: http://www.postgresql.org/message-id/flat/55783940.8080302@wi3ck.info#55783940.8080302@wi3ck.info The short version is that in existing production versions you can easily run in to such symptoms when you get to 8 or more CPU packages. The problem seems to be solved in the development versions of 9.5 (with changes not suitable for back-patching to a stable branch). -- 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