Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUTMm-003Hwa-Dz for pgsql-admin@arkaria.postgresql.org; Thu, 18 Jul 2024 15:48:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sUTMk-000gah-5K for pgsql-admin@arkaria.postgresql.org; Thu, 18 Jul 2024 15:48:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUTMj-000gaY-Lb for pgsql-admin@lists.postgresql.org; Thu, 18 Jul 2024 15:48:22 +0000 Received: from mail2.pscs.co.uk ([178.159.10.131] helo=mail.pscs.co.uk) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUTMg-000DKX-50 for pgsql-admin@lists.postgresql.org; Thu, 18 Jul 2024 15:48:20 +0000 Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=pscs Received: from lmail.pscs.co.uk ([192.168.120.1]) by mail.pscs.co.uk ([192.168.120.185] running VPOP3) with ESMTPSA (TLSv1.3 TLS_AES_256_GCM_SHA384) for ; Thu, 18 Jul 2024 16:48:15 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pscs.co.uk; q=dns/txt; s=lmail; h=Content-Type:Message-ID:Date:MIME-Version:Subject:To:References:From :In-Reply-To:Cc:Content-Transfer-Encoding:Reply-to:Sender; t=1721317335; x=1721922135; bh=qAGBSkkW1cRUWT6LLPbnPBG21yrM2MNhxD7B5Lm3d2A=; b=mqQzPRqlA/rOY/uQgmJNCrqhqT+H1p8f2gR8TZqVWCS25eC09e4xjjoAFScv2hWLvbLI3K5v hwFkH4zQSmONXtWVFUhwkHnxUSam2KUFoL0xG5kr+M/OpibDc7D6A82d6XDHsKepJyWGDWqGMf jwPSOyeVt6BigX97ynb+fa+eE= Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul Received: from [192.168.57.71] ([217.155.111.120] (217-155-111-120.dsl.in-addr.zen.co.uk)) by lmail.pscs.co.uk ([192.168.120.70] running VPOP3) with ESMTPSA (TLSv1.3 TLS_AES_256_GCM_SHA384) for ; Thu, 18 Jul 2024 16:42:14 +0100 Content-Type: multipart/alternative; boundary="------------HbGWi42YtNCK45KRVsnD70aJ" Message-ID: Date: Thu, 18 Jul 2024 16:42:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Seeking Insights on Choosing the Right CPU and RAM for PostgreSQL Setup Content-Language: en-GB To: pgsql-admin@lists.postgresql.org References: From: Paul Smith* In-Reply-To: X-Authenticated-Sender: paul X-Server: VPOP3 Enterprise V8.5 - Registered X-Organisation: Paul Smith Computer Services X-VPOP3Tester: 12 345 X-Authenticated-Sender: pscs List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------HbGWi42YtNCK45KRVsnD70aJ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 18/07/2024 16:33, Veerendra Pulapa wrote: > > Dear PostgreSQL Community, > > > I hope you’re all doing well. We’re currently evaluating hardware > options for our PostgreSQL setup, specifically focusing on CPU and > RAM. We’d love to hear your insights on the following: > Without knowing the details of the workload and data etc, it's pretty much impossible to say. A 1 core CPU at 1.5GHz with 2GB of RAM will happily run PostgreSQL, but may not be able to run it at your desired speed with your workload. Conversely 256 cores at 3GHz with 1TB of RAM will also happily run PostgreSQL, but may be overkill. Also, from experience, disk system is at least as important as CPU/RAM (until you get to the point where the RAM will hold the whole database in cache). Running a fast CPU with lots of RAM won't be any use if you're running it on 5400 RPM SATA drives in a RAID 5 array.... Paul --------------HbGWi42YtNCK45KRVsnD70aJ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 18/07/2024 16:33, Veerendra Pulapa wrote:

Dear PostgreSQL Community,


I hope you’re all doing well. We’re currently evaluating hardware options for our PostgreSQL setup, specifically focusing on CPU and RAM. We’d love to hear your insights on the following:


Without knowing the details of the workload and data etc, it's pretty much impossible to say.

A 1 core CPU at 1.5GHz with 2GB of RAM will happily run PostgreSQL, but may not be able to run it at your desired speed with your workload.

Conversely 256 cores at 3GHz with 1TB of RAM will also happily run PostgreSQL, but may be overkill.


Also, from experience, disk system is at least as important as CPU/RAM (until you get to the point where the RAM will hold the whole database in cache). Running a fast CPU with lots of RAM won't be any use if you're running it on 5400 RPM SATA drives in a RAID 5 array....


Paul


--------------HbGWi42YtNCK45KRVsnD70aJ--