Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 29064632CB2 for ; Sun, 14 Feb 2010 12:36:50 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 91304-06 for ; Sun, 14 Feb 2010 16:36:39 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id 7B184632DAC for ; Sun, 14 Feb 2010 12:36:39 -0400 (AST) Received: by vws20 with SMTP id 20so1328060vws.19 for ; Sun, 14 Feb 2010 08:36:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :content-type:content-transfer-encoding:mime-version:subject:date :x-mailer; bh=tAdU037k/WJgLqwcBbohX9PqzwCvnaNGeIEkRiEWghs=; b=nz5qcrGu2smJm0nQJEAArPzGRYgGAo5QqGz4rqqe28obZ7MvjzVD/wjI3wTSXNAHX8 VbKo8GFeRk0Ig4cEQ2exki1zsOZb2BYPOxgZ9mgs4gsVX+lm8Py+sm4cNABOMfI4tc/p q9XZJEpGKBVkeVgnvq/SD0prHial2Yrd/rVf0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding :mime-version:subject:date:x-mailer; b=nQY40GGkLJJAZCz3KJASFhmb2ezY31KcU0QoN8X/WFccsafroUjWFyppKpMjcW8+p/ mJlDZp3tTRn24I5EYk8vsnmZSgWjfNqcDbNS0ppkrK0cK5f0fGd6tzM6wLFxDquTOFhz InL5K3X56mKv3LGUYH+qCr6XvvkdFoW75ok4s= Received: by 10.220.108.218 with SMTP id g26mr2347216vcp.104.1266165398477; Sun, 14 Feb 2010 08:36:38 -0800 (PST) Received: from ?192.168.2.2? ([88.237.217.62]) by mx.google.com with ESMTPS id 24sm39208447vws.13.2010.02.14.08.36.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 14 Feb 2010 08:36:37 -0800 (PST) Message-Id: <4DA8D3EC-9868-4A6D-8806-F0534C55D2C6@gmail.com> From: Reydan Cankur To: pgsql-performance@postgresql.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: PostgreSQL on SMP Architectures Date: Sun, 14 Feb 2010 18:36:24 +0200 X-Mailer: Apple Mail (2.935.3) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/225 X-Sequence-Number: 37646 Hi, I have seen some work done about scaling PostgreSQL on SMP machines and see that PostgreSQL has been executed on several numbers of cores. I have some questions about scaling PostgreSQL on SMP architectures. System Details that I am running PostgreSQL-8.4.0: Server: HP Integrity Superdome SD32B Processor: Intel Itanium2 1.6 GHz (dual-core) Number of processors: 32 Number of compute cores: 64 Memory architecture: Shared Memory amount: 128 GB Disk amount: 4.6 TB High performance network: InfiniBand 20 Gbps Operating system: RHEL 5.1 IA64 Question 1) How can I run PostgreSQL on 2,4,8,16,32 and 64 cores and get performance results? I have seen some work about scaling POstgreSQL on SMP architectures and in these slides there were performance results for PostgreSQL running on different number of cpu cores. I want to execute PostgreSQL for different number of cpu cores like 2,4,8,16,32,64 on above server. But I do not know how to compile or run PostgreSQL on multiple cpu cores. What is the exact command to tell Postgres to run on specified number of cores? I need to run Postgres on multiple CPU cores and document this work. Question 2)Are there any official benchmarks for PostgreSQL performance measurements? I mean when someone wants to run an official performance test on PostgreSQL which queries and tables must be used. I have executed my queries on a 5 million record table in order to measure performance, but I also want to use the official methods. Question 3) How can I change the allocated memory and measure the performance of PostgreSQL? Thanks for all answers, Reydan