Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-performance-owner+M55060=pgsql-performance-ar@postgresql.org>)
	id 1dDEaw-0006sr-4y
	for pgsql-performance@arkaria.postgresql.org; Tue, 23 May 2017 18:31:46 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-performance-owner+M55060=pgsql-performance-ar@postgresql.org>)
	id 1dDEav-0004Hf-Im
	for pgsql-performance@arkaria.postgresql.org; Tue, 23 May 2017 18:31:45 +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_2)
	(envelope-from <jarek@poczta.srv.pl>)
	id 1dDEZA-00014L-J2
	for pgsql-performance@postgresql.org; Tue, 23 May 2017 18:29:56 +0000
Received: from mail.srv.pl ([2001:1a68:0:c::4a])
	by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.84_2)
	(envelope-from <jarek@poczta.srv.pl>)
	id 1dDEZ7-0004CE-Lp
	for pgsql-performance@postgresql.org; Tue, 23 May 2017 18:29:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=srv.pl;
 s=dkim;
	h=Content-Transfer-Encoding:Mime-Version:Content-Type:Date:To:From:Subject:Message-ID;
 bh=RMIAc6XC3jA+QDrBTbAwX8roESUj8NAZTynJ9f9vm1o=;
	b=viuIlFK2E0phPC/Tf0QxwlErFsfKpAbO7z+EMe85iGM2MRX5jc4sUUcjbD/bmrO+EfL2W4EMEQHPQ6caCHJnRIpj5UTseTEorpYA6t1up3vT0Mx0ScGoA/x1IN1ODWIIXNe2hoqCJx4kCL3f+7kcWuzfPNug85KCdHn57cFFv08=;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
 d=bodygloveoptrix.pl; s=dkim;
	h=Content-Transfer-Encoding:Mime-Version:Content-Type:Date:To:From:Subject:Message-ID;
 bh=RMIAc6XC3jA+QDrBTbAwX8roESUj8NAZTynJ9f9vm1o=;
	b=HK64PCib5BITapG1x14We+2jkpht0p58iwYc6NYO1BcK5ZbiAlYC/8Ts0cNA8O8/i/64aXps32fLXKg6/SEiJe+zl8LrXlGWFZhswoiq4gLz/gYETAq4NyoFby5WWf86Ga8FmyJdx25DLQBtu8mwmRNH3hqGjJPjRFVO9nPH8C4=;
Message-ID: <1495564174.6168.10.camel@sem-jarek-01.prv>
Subject: More cores or higer frequency ?
From: Jarek <jarek@poczta.srv.pl>
To: pgsql-performance@postgresql.org
Date: Tue, 23 May 2017 20:29:34 +0200
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4-0ubuntu2 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.9
X-Spam-Level: --
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Hello!

I've heavy loaded PostgreSQL server, which I want to upgrade, so it will
handle more traffic. Can I estimate what is better: more cores or
higher frequency ? I expect that pg_stat should give some tips, but
don't know where to start...

best regards
Jarek



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