Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dDGER-0006xn-1J for pgsql-performance@arkaria.postgresql.org; Tue, 23 May 2017 20:16:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dDGEQ-0002S6-KX for pgsql-performance@arkaria.postgresql.org; Tue, 23 May 2017 20:16:38 +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_2) (envelope-from ) id 1dDGCf-0007h5-6p for pgsql-performance@postgresql.org; Tue, 23 May 2017 20:14:49 +0000 Received: from mail.srv.pl ([2001:1a68:0:c::4a]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dDGCa-0003pp-6U for pgsql-performance@postgresql.org; Tue, 23 May 2017 20:14:48 +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:References:In-Reply-To:Date:To:From:Subject:Message-ID; bh=AEAjHTSfgYRZvk10Kte5Cnh9CMi0Qb8ff9Wy8aLp7SA=; b=Sm1sEsHcb8pP0bDOzxsL2SrJTBm/o9/gJjnF0WnC2ci9GU0+IskIJnxuFQ/m2KTaTMVNqNZkQUJwjAVFf9Dk3U3roh5b1TF7sMFWPg9mU8POi6WyuzSpLdL4uHo/xkqZuQME5ixkKnwZmu/u5hHWhqexzldy6EvUDvi1mXoEf2k=; 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:References:In-Reply-To:Date:To:From:Subject:Message-ID; bh=AEAjHTSfgYRZvk10Kte5Cnh9CMi0Qb8ff9Wy8aLp7SA=; b=TcYOyHD03qJT2+iKZrDK9yG7os4phMt5+pnBTo629RBKRqbedVbLdvVwbHgB+VP00oUJ6YVTRZvDrgs4teNRhXIVeNCW4w1Ocrsx2ITHZmFfmal3iFl3Ez/P+e1+J0N7CRCTh3FaS9iBxWJ2DNRKz1uULidLRl/NO2jwAusI1Kg=; Message-ID: <1495570454.6168.44.camel@sem-jarek-01.prv> Subject: Re: More cores or higer frequency ? From: Jarek To: pgsql-performance@postgresql.org Date: Tue, 23 May 2017 22:14:14 +0200 In-Reply-To: References: <1495564174.6168.10.camel@sem-jarek-01.prv> 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: 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 Dnia 2017-05-23, wto o godzinie 11:39 -0700, Steve Crawford pisze: > The answer, as always, is "it depends." > > > Can you give us an overview of your setup? The appropriate setup for > small numbers of long-running analytical queries (typically faster > CPUs) will be different than a setup for handling numerous > simultaneous connections (typically more cores). I have pool of clients (~30) inserting to database about 50 records per second (in total from all clients) and small numer (<10) clients querying database for those records once per 10s. Other queries are rare and irregular. The biggest table has ~ 100mln records (older records are purged nightly). Database size is ~13GB. I near future I'm expecting ~150 clients and 250 inserts per second and more clients querying database. Server is handling also apache with simple web application written in python. For the same price, I can get 8C/3.2GHz or 14C/2.6GHz. Which one will be better ? > > But CPU is often not the limiting factor. With a better understanding > of your needs, people here can offer suggestions for memory, storage, > pooling, network, etc. > > > Cheers, > Steve > > > > On Tue, May 23, 2017 at 11:29 AM, Jarek wrote: > 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 > > -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance