Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h1Oj0-00066r-30 for pgsql-performance@arkaria.postgresql.org; Wed, 06 Mar 2019 05:04:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h1Oiy-0006k9-Hc for pgsql-performance@arkaria.postgresql.org; Wed, 06 Mar 2019 05:04:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h1Oiy-0006k2-3j for pgsql-performance@lists.postgresql.org; Wed, 06 Mar 2019 05:04:12 +0000 Received: from mail-pg1-x531.google.com ([2607:f8b0:4864:20::531]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h1Oir-0008C3-1t for pgsql-performance@postgresql.org; Wed, 06 Mar 2019 05:04:10 +0000 Received: by mail-pg1-x531.google.com with SMTP id l11so7345481pgq.10 for ; Tue, 05 Mar 2019 21:04:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QLvHPlc7W7m0HGbgs2rciYaxATVyI6dPrOzlkoJfT14=; b=RG8+VU69ZFL5u7Ei/aNx2O/6XsP88zSFrPyRoHXKHGGzJz9BY/6tSRBeYu9gq3f72F iU15LR/Sk8zRocvtuhOJvnLr3Ly6vWQrfVRonxSM7/FzrAkUs9JQuUyft1xLM0LVf0wq t1HZItVvDnr4ggSUnrzk5u2t+XjiKLJrhx9vNCJ9b8pgeYmjs9+E+pcDFDkk70WGFx0e sitDCc+h0emv0NZ4aOPUjP9+GqX9WmNPZnogHlf0XhQni+mdrMOD6cLqCY8P5aWuVkLj D1KJc/gFjv25kz59M6/EiXDDbJWfjdzEewvJk0Jy+fJZ7lQAYmbQSydOU0nPjVxFATyg lOug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QLvHPlc7W7m0HGbgs2rciYaxATVyI6dPrOzlkoJfT14=; b=fLnmG/o1FD/9VnIjkwwXA2FR3hyeQKTGJK+O8EiIrSBlNMWFvNtIRuoZxqIZlCaMPB V2ngZjxWCiPBTiFUNhOzT/9l2VySQqp/zPlekY9UT052vvYfXGaHu0o8k3OAlSwnaM3T BU4S10cpyoTwV3mIjpyQJR37z0vQ88D5EWmthXqDLvIPYLS+kGpjbonAz5b54KIQNPmC eeRcoKlsa2+vLk1cwQBT985PWOAj23+TTF/tAiX3MU0NQWaE3EUKzfK3xkIWR7vMbUB6 RsDEiJXNBFXa8193OOWgcFeNodlvBBlZrhqv8KG1VUP5Lu7A0GgCyYo7H2YTUXO0uJ2g V9ZA== X-Gm-Message-State: APjAAAWWG37RhddPU8EvhzOjm7a7qzE9kYXlK2kS6b7YWGNvDApbm511 whKQr9OpopduM/v7uKWNK7IgnHFs X-Google-Smtp-Source: APXvYqzGCOLac4ryFE4b0b5mKMNOA7RdOaflcsAki56YxNYtiNscrqBvGxifXayxb5YANOMOGiSf/A== X-Received: by 2002:a62:e082:: with SMTP id d2mr5621125pfm.240.1551848643759; Tue, 05 Mar 2019 21:04:03 -0800 (PST) Received: from ?IPv6:2601:603:80:90a:6849:1a01:582e:589c? ([2601:603:80:90a:6849:1a01:582e:589c]) by smtp.gmail.com with ESMTPSA id f3sm1166862pfn.100.2019.03.05.21.04.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2019 21:04:02 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Server upgrade advice [xpost] From: Ian Harding X-Mailer: iPhone Mail (16C101) In-Reply-To: <20190305220326.4qtowuv2s4zdpgc5@campbell-lange.net> Date: Tue, 5 Mar 2019 21:04:01 -0800 Cc: pgsql-performance@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <37E61451-B744-4C7D-834C-BAA917ADE243@gmail.com> References: <20190305220326.4qtowuv2s4zdpgc5@campbell-lange.net> To: Rory Campbell-Lange List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk The two major version upgrade will bring many happy returns. That=E2=80=99s= all I can contribute.=20 > On Mar 5, 2019, at 2:03 PM, Rory Campbell-Lange w= rote: >=20 > Apologies for the cross-post to the general list. I realised I should > have (possibly?) posted here instead. Advice gratefully received. >=20 > We've been happy running a database server and replica for some years > with the following details and specs: >=20 > postgres 9.5 (currently) > supermicro X9DRD-7LN4F > LSI Megaraid MR9261-8i with BBU > 250gb raid 1 / > 224gb raid 10 /db > 126GB RAM (1066Mhz DDR3) > 2 x Xeon E5-2609 v2 @ 2.5GHz >=20 > Services on the server are scaling up quite quickly, so we are running > out of disk space for the several hundred databases in the cluster. > While the disk space is fairly easy to solve, our main issue is CPU > hitting daily 5 minute peaks of 65% plus under load for complex plpgsql > queries, causing query backups. While we don't often spill queries to > disk, running out of RAM is an incipient problem too.=20 >=20 > While we could split the cluster there are some management issues to do > with that, together with our having a policy of local and remote > replicas.=20 >=20 > Consequently we're thinking of the following replacement servers: >=20 > postgres 11 (planned) > supermicro 113TQ-R700W=20 > LSI MegaRAID 9271-8i SAS/SATA RAID Controller, 1Gb DDR3 Cache (PCIE- Ge= n 3) > 500gb raid 1 / > 2tb raid 10 /db > with "zero maintenance flash cache protection" > 256GB RAM (2666MHz DDR4) > 2x E5-2680 v4 Intel Xeon, 14 Cores, 2.40GHz, 35M Cache, >=20 > This configuration gives us lots more storage, double the RAM (with 8 > slots free) and just under 4x CPU (according to passmark) with lots more > cores. >=20 > We're hoping to get two to three years of service out of this upgrade, > but then will split the cluster between servers if demand grows more > than we anticipate. >=20 > Any comments on this upgrade, strategy or the "zero maintenance" thingy > (instead of a BBU) would be much appreciated. >=20 > Rory >=20