Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XUh59-0007o0-N6 for pgsql-performance@arkaria.postgresql.org; Thu, 18 Sep 2014 19:09:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XUh59-0002uF-3u for pgsql-performance@arkaria.postgresql.org; Thu, 18 Sep 2014 19:09:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XUh58-0002u9-8K for pgsql-performance@postgresql.org; Thu, 18 Sep 2014 19:09:30 +0000 Received: from smtp-o-3.desy.de ([2001:638:700:1038::1:9c]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XUh55-0003RN-1d for pgsql-performance@postgresql.org; Thu, 18 Sep 2014 19:09:28 +0000 Received: from smtp-map-3.desy.de (smtp-map-3.desy.de [131.169.56.68]) by smtp-o-3.desy.de (DESY-O-3) with ESMTP id D049B280370 for ; Thu, 18 Sep 2014 21:09:24 +0200 (CEST) Received: from ZITSWEEP1.win.desy.de (zitsweep1.win.desy.de [131.169.97.95]) by smtp-map-3.desy.de (DESY_MAP_3) with ESMTP id C12971101 for ; Thu, 18 Sep 2014 21:09:24 +0200 (MEST) Received: from smtp-intra-1.desy.de (lb-40-26.desy.de) by ZITSWEEP1.win.desy.de (Clearswift SMTPRS 5.5.0) with ESMTP id ; Thu, 18 Sep 2014 21:09:24 +0200 Received: from z-mta-3.desy.de (z-mta-3.desy.de [131.169.55.137]) by smtp-intra-1.desy.de (DESY-INTRA-1) with ESMTP id 615C63E905; Thu, 18 Sep 2014 21:09:24 +0200 (MEST) Received: from z-mta-3.desy.de (localhost [127.0.0.1]) by z-mta-3.desy.de (Postfix) with ESMTP id 5AE4A400C0; Thu, 18 Sep 2014 21:09:24 +0200 (CEST) Received: from z-mta-3.desy.de (localhost [127.0.0.1]) by z-mta-3.desy.de (Postfix) with ESMTP id 49DE9400C4; Thu, 18 Sep 2014 21:09:24 +0200 (CEST) Received: from z-mbx-2.desy.de (z-mbx-2.desy.de [131.169.55.140]) by z-mta-3.desy.de (Postfix) with ESMTP id 421F5400C0; Thu, 18 Sep 2014 21:09:24 +0200 (CEST) Date: Thu, 18 Sep 2014 21:09:24 +0200 (CEST) From: "Mkrtchyan, Tigran" To: Josh Berkus Cc: pgsql-performance@postgresql.org Message-ID: <1743190394.45544.1411067364145.JavaMail.zimbra@desy.de> In-Reply-To: <541B1C50.7010806@agliodbs.com> References: <45142416.42827.1411033201079.JavaMail.zimbra@desy.de> <88549888.42916.1411034301200.JavaMail.zimbra@desy.de> <747323809.44735.1411052960344.JavaMail.zimbra@desy.de> <541B1C50.7010806@agliodbs.com> Subject: Re: postgres 9.3 vs. 9.4 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.0.7_GA_6021 (ZimbraWebClient - FF35 (Mac)/8.0.7_GA_6021) Thread-Topic: postgres 9.3 vs. 9.4 Thread-Index: 67xz9HJCdcMWeAsP9vtAbJKlQdsFYg== X-Pg-Spam-Score: -1.6 (-) 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 ----- Original Message ----- > From: "Josh Berkus" > To: pgsql-performance@postgresql.org > Sent: Thursday, September 18, 2014 7:54:24 PM > Subject: Re: [PERFORM] postgres 9.3 vs. 9.4 > > On 09/18/2014 08:09 AM, Mkrtchyan, Tigran wrote: > >>> 9.4beta2: > >>> > > > >> > ... > >> > > >>> > > 0.957854 END; > >>> > > > >> > > >> > Looks like IO. > > Postgres internal IO? May be. We get 600MB/s on this SSDs. > > While it's possible that this is a Postgres issue, my first thought is > that the two SSDs are not actually identical. The 9.4 one may either > have a fault, or may be mostly full and heavily fragmented. Or the Dell > PCIe card may have an issue. We have tested both SSDs and they have identical IO characteristics and as I already mentioned, both databases are fresh, including filesystem. > > You are using "scale 1" which is a < 1MB database, and one client and 1 > thread, which is an interesting test I wouldn't necessarily have done > myself. I'll throw the same test on one of my machines and see how it does. this scenario corresponds to our use case. We need a high transaction rate per for a single client. Currently I can get only ~1500 tps. Unfortunately, posgtress does not tell me where the bottleneck is. Is this is defensively not the disk IO. Thanks for the help, Tigran. > > -- > Josh Berkus > PostgreSQL Experts Inc. > http://pgexperts.com > > > -- > 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