Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 3744412B5668 for ; Thu, 5 Jul 2012 21:58:03 -0300 (ADT) Received: from mail-yw0-f46.google.com ([209.85.213.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Smwrw-0007LK-VB for pgsql-performance@postgresql.org; Fri, 06 Jul 2012 00:58:02 +0000 Received: by yhmm54 with SMTP id m54so8879255yhm.19 for ; Thu, 05 Jul 2012 17:57:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=skVD3C6WzbAbImbpdki8RqpSVottubldoyn8wIdyKIw=; b=CU0hxidYIZyD17A8wosuUPOK59+QFagHRNSG7xvFVmvea7yTEPrQPU9Kzt3RNXGoas vUR16AUFaSO81OLgWfpTfsAREKt5N3FQCXmyh4Z53sYnl0t+rgr9iFK2DS/dU9oMVUxU QFbxcFr7Go5qzzfbTB93tKn87hxdYTjad9Nhm4w6oogtGCtE0oVqVV6OXnYpbtNRJT+G 118AC7xxxqCi+D8a/3u19/qi4/hi5PwW9qEBtHGG0ouXmPHGoC5vYA0cDojDerU2s7WF TuKy2Ui0f/gWk3+uWfNOZ8m1jzZ8C101EWO2oX2U/b+jlVHlwwocI6MgjS+iAhTCApwj n7cQ== Received: by 10.66.84.67 with SMTP id w3mr41543629pay.70.1341536267071; Thu, 05 Jul 2012 17:57:47 -0700 (PDT) Received: from ayaki.localdomain (124-169-169-118.dyn.iinet.net.au. [124.169.169.118]) by mx.google.com with ESMTPS id jp10sm20743436pbb.16.2012.07.05.17.57.43 (version=SSLv3 cipher=OTHER); Thu, 05 Jul 2012 17:57:46 -0700 (PDT) Message-ID: <4FF63804.2060107@ringerc.id.au> Date: Fri, 06 Jul 2012 08:57:40 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Samuel Gendler CC: Reza Taheri , Robert Klemme , "pgsql-performance@postgresql.org" Subject: Re: The need for clustered indexes to boost TPC-V performance References: <66CE997FB523C04E9749452273184C6C137CB88A86@exch-mbx-113.vmware.com> <66CE997FB523C04E9749452273184C6C137CB88CF9@exch-mbx-113.vmware.com> <66CE997FB523C04E9749452273184C6C137CB88D2C@exch-mbx-113.vmware.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------060007030201080704020201" X-Gm-Message-State: ALoCoQlxS09+nN+mKqI8IWvHyLjVsPnf6qkIVZt/Y1LegJ8j25GHCExpmAyZtyugHU9qflXKSJIa X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201207/30 X-Sequence-Number: 47211 This is a multi-part message in MIME format. --------------060007030201080704020201 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit On 07/06/2012 04:52 AM, Samuel Gendler wrote: > > > On Thu, Jul 5, 2012 at 1:37 PM, Reza Taheri > wrote: > > > I provided more config details in an earlier email. > > > > I hate to disagree, but unless I didn't get a message sent to the list It looks like that might be the case. I got a message with Message-ID 66CE997FB523C04E9749452273184C6C137CB88CDD@exch-mbx-113.vmware.com sent at Thu, 5 Jul 2012 11:33:46 -0700 that contained the basic info, postgresql.conf, etc. Belated, but it was sent. I can't find this message in the archives and the copy I got came direct to me via cc, so I suspect our friendly mailing list system has silently held it for moderation due to size/attachment. I'll reproduce the content below, followed by an inline copy of the postgresql.conf with only changed lines: On 07/06/2012 02:33 AM, Reza Taheri wrote: > > OK, some config details. > > We are using: > > ·Two blades of an HP BladeSystem c-Class c7000 with 2-socket Intel > E5520 (Nehalem-EP) processors and 48GB of memory per blade > > o8 cores, 16 threads per blade > > o48GB of RAM per blade > > ·Storage was an EMC VNX5700 with 14 SSDs fronting 32 15K RPM drives > > ·The Tier B database VM was alone on a blade with 16 vCPUs, 40GB of > memory, 4 virtual drives with various RAID levels > > ·The driver and Tier A VMs were on the second blade > > oSo we set PGHOST on the client system to point to the server > > ·RHEL 6.1 > > ·PostgreSQL 8.4 > > ·unixODBC 2.3.2 > > We stuck with PGSQL 8.4 since it is the stock version shipped with > RHEL 6. I am building a new, larger testbed, and will switch to PGSQL > 9 with that. > > postgresql.conf: [craig@ayaki ~]$ egrep -v '(^\s*#)|(^\s*$)' /tmp/postgresql2.conf | cut -d '#' -f 1 listen_addresses = '*' max_connections = 320 shared_buffers = 28GB temp_buffers = 200MB work_mem = 10MB maintenance_work_mem = 10MB bgwriter_delay = 10ms bgwriter_lru_maxpages = 20 wal_buffers = 16MB checkpoint_segments = 128 checkpoint_timeout = 30min checkpoint_completion_target = 0.9 default_statistics_target = 10000 logging_collector = on log_directory = 'pg_log' log_filename = 'postgresql-%a.log' log_truncate_on_rotation = on log_rotation_age = 1d log_rotation_size = 0 datestyle = 'iso, mdy' lc_messages = 'en_US.UTF-8' lc_monetary = 'en_US.UTF-8' lc_numeric = 'en_US.UTF-8' lc_time = 'en_US.UTF-8' default_text_search_config = 'pg_catalog.english' --------------060007030201080704020201 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 07/06/2012 04:52 AM, Samuel Gendler wrote:


On Thu, Jul 5, 2012 at 1:37 PM, Reza Taheri <rtaheri@vmware.com> wrote:

I provided more config details in an earlier email.

 



I hate to disagree, but unless I didn't get a message sent to the list

It looks like that might be the case. I got a message with Message-ID 66CE997FB523C04E9749452273184C6C137CB88CDD@exch-mbx-113.vmware.com sent at Thu, 5 Jul 2012 11:33:46 -0700 that contained the basic info, postgresql.conf, etc. Belated, but it was sent. I can't find this message in the archives and the copy I got came direct to me via cc, so I suspect our friendly mailing list system has silently held it for moderation due to size/attachment.


I'll reproduce the content below, followed by an inline copy of the postgresql.conf with only changed lines:

On 07/06/2012 02:33 AM, Reza Taheri wrote:

OK, some config details.

We are using:

 

·         Two blades of an HP BladeSystem c-Class c7000 with 2-socket Intel E5520 (Nehalem-EP) processors and 48GB of memory per blade

o   8 cores, 16 threads per blade

o   48GB of RAM per blade

·         Storage was an EMC VNX5700 with 14 SSDs fronting 32 15K RPM drives

·         The Tier B database VM was alone on a blade with 16 vCPUs, 40GB of memory, 4 virtual drives with various RAID levels

·         The driver and Tier A VMs were on the second blade

o   So we set PGHOST on the client system to point to the server

·         RHEL 6.1

·         PostgreSQL 8.4

·         unixODBC 2.3.2

 

We stuck with PGSQL 8.4 since it is the stock version shipped with RHEL 6. I am building a new, larger testbed, and will switch to PGSQL 9 with that.

 


postgresql.conf:

[craig@ayaki ~]$ egrep -v '(^\s*#)|(^\s*$)' /tmp/postgresql2.conf  | cut -d '#' -f 1
listen_addresses = '*'           
max_connections = 320           
shared_buffers = 28GB           
temp_buffers = 200MB           
work_mem = 10MB               
maintenance_work_mem = 10MB       
bgwriter_delay = 10ms           
bgwriter_lru_maxpages = 20       
wal_buffers = 16MB           
checkpoint_segments = 128       
checkpoint_timeout = 30min       
checkpoint_completion_target = 0.9   
default_statistics_target = 10000   
logging_collector = on           
log_directory = 'pg_log'       
log_filename = 'postgresql-%a.log'   
log_truncate_on_rotation = on       
log_rotation_age = 1d           
log_rotation_size = 0           
datestyle = 'iso, mdy'
lc_messages = 'en_US.UTF-8'           
lc_monetary = 'en_US.UTF-8'           
lc_numeric = 'en_US.UTF-8'           
lc_time = 'en_US.UTF-8'               
default_text_search_config = 'pg_catalog.english'


--------------060007030201080704020201--