X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 471FED1B494 for ; Wed, 10 Dec 2003 05:56:47 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 87267-08 for ; Wed, 10 Dec 2003 01:56:16 -0400 (AST) Received: from linda-1.paradise.net.nz (bm-1a.paradise.net.nz [202.0.58.20]) by svr1.postgresql.org (Postfix) with ESMTP id C2A78D1B4AE for ; Wed, 10 Dec 2003 01:56:14 -0400 (AST) Received: from smtp-3.paradise.net.nz (smtp-3a.paradise.net.nz [202.0.32.196]) by linda-1.paradise.net.nz (Paradise.net.nz) with ESMTP id <0HPO00BD80HQSW@linda-1.paradise.net.nz> for pgsql-performance@postgresql.org; Wed, 10 Dec 2003 18:56:14 +1300 (NZDT) Received: from paradise.net.nz (203-79-100-38.adsl.paradise.net.nz [203.79.100.38]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 05519ADF50 for ; Wed, 10 Dec 2003 18:56:14 +1300 (NZDT) Date: Wed, 10 Dec 2003 18:56:38 +1300 From: Mark Kirkwood Subject: Solaris Performance (Again) To: pgsql-performance@postgresql.org Message-id: <3FD6B596.8090803@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031008 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/166 X-Sequence-Number: 5026 This is a well-worn thread title - apologies, but these results seemed interesting, and hopefully useful in the quest to get better performance on Solaris: I was curious to see if the rather uninspiring pgbench performance obtained from a Sun 280R (see General: ATA Disks and RAID controllers for database servers) could be improved if more time was spent tuning. With the help of a fellow workmate who is a bit of a Solaris guy, we decided to have a go. The major performance killer appeared to be mounting the filesystem with the logging option. The next most significant seemed to be the choice of sync_method for Pg - the default (open_datasync), which we initially thought should be the best - appears noticeably slower than fdatasync. We also tried changing some of the tuneable filesystem options using tunefs - without any measurable effect. Are Pg/Solaris folks running with logging on and sync_method default out there ? - or have most of you been through this already ? Pgbench Results (no. clients and transactions/s ) : Setup 1: filesystem mounted with logging No. tps ----------- 1 17 2 17 4 22 8 22 16 28 32 32 64 37 Setup 2: filesystem mounted without logging No. tps ----------- 1 48 2 55 4 57 8 62 16 65 32 82 64 95 Setup 3 : filesystem mounted without logging, Pg sync_method = fdatasync No. tps ----------- 1 89 2 94 4 95 8 93 16 99 32 115 64 122 Note : The Pgbench runs were conducted using -s 10 and -t 1000 -c 1->64, 2 - 3 runs of each setup were performed (averaged figures shown). Mark