X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id BD3DBD83E4 for ; Fri, 11 Nov 2005 14:42:19 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 85934-05 for ; Fri, 11 Nov 2005 18:42:17 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.eulerhermes.pl (host-ip43-68.crowley.pl [85.128.68.43]) by svr1.postgresql.org (Postfix) with ESMTP id 2C1F0D7967 for ; Fri, 11 Nov 2005 14:42:17 -0400 (AST) Received: from stunnel-ns1.warszawa-ext ([192.168.69.4] helo=[127.0.0.1] ident=nobody) by mail.eulerhermes.pl with esmtpa (Exim 4.42) id 1Eadqm-0008Av-RM; Fri, 11 Nov 2005 19:42:15 +0100 Message-ID: <4374E57F.5030201@eulerhermes.pl> Date: Fri, 11 Nov 2005 19:39:59 +0100 From: Marcin Giedz User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Tom Lane , "Jim C. Nasby" CC: pgsql-admin@postgresql.org Subject: Re: Xeon vs Opteron - second revision - tests and questions References: <200511091526.51685.marcin.giedz@eulerhermes.pl> <18347.1131563949@sss.pgh.pa.us> In-Reply-To: <18347.1131563949@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.021 required=5 tests=[AWL=0.021] X-Spam-Score: 0.021 X-Spam-Level: X-Archive-Number: 200511/138 X-Sequence-Number: 19511 Hello, First of all: many thanks Tom for pointed me out what I made wrong and Jim for 'spikes'. I made some new tests: available at http://85.128.68.44 What have changed since last time: - database engine - now it's 8.1.0 - number of clients - "-c 20 " - number of transactions - "-t 1000" Really seems that you have made EXCELLENT work. Performance increased about 25% in 8.1.0. I also made some changes related with bg_write and wal (according to Jim): bg_writer_all_percent = 0.433 bg_writer_all_maxpages = 15 wal_buffers = 8192 However I still can see 'spikey' performance but not as much as before changes. What can I do more to eliminate or smooth these spikes? I tried to increase bg_writer_all_xxx parameters but.... spikes still exists ;). Regards, Marcin >This is pretty nearly an ideal example of how NOT to use pg_bench :-( > >In the first place, don't use a number of clients (-c) much exceeding >the scale factor (-s). If you do, then almost all you are measuring is >the effects of update contention. There are only scale-factor rows in >the branches table, and every pgbench transaction wants to update one of >the branches rows, so with -c 100 and -s 20 there are on average going >to be 5 transactions simultaneously trying to modify the same branches >row. 4 of them are going to be waiting. Does that really correspond >to a real-world situation that you want to optimize? > >In the second place, you need a run length considerably longer than >-t 100 to avoid getting swamped by noise of startup/shutdown overhead. >I usually use at least -t 1000 if I want repeatable numbers. > >BTW, PG 8.1 will probably do better than 8.0 on multi-CPU hardware. > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > > >