Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id CB9B49FB473 for ; Fri, 30 Mar 2007 17:42:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 38173-01 for ; Fri, 30 Mar 2007 17:42:53 -0300 (ADT) X-Greylist: delayed 00:17:41.821933 by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 7E3FA9FB32D for ; Fri, 30 Mar 2007 17:42:54 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from cse.ohio-state.edu (mail.cse.ohio-state.edu [164.107.123.5]) by svr4.postgresql.org (Postfix) with ESMTP id 21F055AF8DD for ; Fri, 30 Mar 2007 20:25:11 +0000 (GMT) Received: from [164.107.116.241] (jason.cse.ohio-state.edu [164.107.116.241]) (authenticated bits=0) by cse.ohio-state.edu (8.12.11.20060308/8.12.11) with ESMTP id l2UKP7Bt020768 for ; Fri, 30 Mar 2007 16:25:07 -0400 (EDT) Message-ID: <460D7220.9010302@cse.ohio-state.edu> Date: Fri, 30 Mar 2007 16:25:04 -0400 From: Xiaoning Ding User-Agent: Thunderbird 1.5.0.10 (X11/20070301) MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: scalablility problem Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200703/455 X-Sequence-Number: 23860 Hi all, When I run multiple TPC-H queries (DBT3) on postgresql, I found the system is not scalable. My machine has 8GB memory, and 4 Xeon Dual Core processor ( 8 cores in total). OS kernel is linux 2.6.9. Postgresql is 7.3.18. I run multiple q2 queries simultaneously. The results are: 1 process takes 0.65 second to finish. 2 processes take 1.07 seconds. 4 processes take 4.93 seconds. 8 processes take 16.95 seconds. For 4-process case and 8-process case, queries takes even more time than they are executed serially one after another. Because the system has 8GB memory, which is much bigger than the DB size(SF=1), and I warmed the cache before I run the test, I do not think the problem was caused by disk I/O. I think it might be caused by some contentions. But I do not know postgresql much. May anybody give me some clue to find the reasons? Thanks! Xiaoning