Received: from makus.postgresql.org ([98.129.198.125])
by malur.postgresql.org with esmtp (Exim 4.72)
(envelope-from ) id 1T5F9Q-0002or-J8
for pgsql-performance@postgresql.org; Sat, 25 Aug 2012 12:07:40 +0000
Received: from linux3.internet1.de ([62.146.37.208])
by makus.postgresql.org with esmtp (Exim 4.72)
(envelope-from ) id 1T5F9O-00038k-L5
for pgsql-performance@postgresql.org; Sat, 25 Aug 2012 12:07:39 +0000
Received: (qmail 28877 invoked from network); 25 Aug 2012 14:07:35 +0200
Received: from hsi-kbw-109-192-091-178.hsi6.kabel-badenwuerttemberg.de (HELO
?192.168.1.116?) (109.192.91.178)
by linux3.internet1.de with ESMTPA; 25 Aug 2012 14:07:35 +0200
From: Felix Schubert
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Slow Performance on a XEON E5504
Message-Id: <28C5C61F-5ADE-4AD5-9E27-61DC482398A2@fescon.de>
Date: Sat, 25 Aug 2012 14:07:34 +0200
To: "pgsql-performance@postgresql.org"
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
X-Pg-Spam-Score: -1.9 (-)
X-Archive-Number: 201208/161
X-Sequence-Number: 47699
Hello List,
I've got a system on a customers location which has a XEON E5504 @ =
2.00GHz Processor (HP Proliant)
It's postgres 8.4 on a Debian Squeeze System running with 8GB of ram:
The Postgres Performance on this system measured with pgbench is very =
poor:
transaction type: TPC-B (sort of)
scaling factor: 1
query mode: simple
number of clients: 40
number of transactions per client: 100
number of transactions actually processed: 4000/4000
tps =3D 158.283272 (including connections establishing)
tps =3D 158.788545 (excluding connections establishing)
The same database on a Core i7 CPU 920 @ 2.67GHz, 8 cores with 8GB RAM =
same distro and Postgresql Version is much faster:
transaction type: TPC-B (sort of)
scaling factor: 1
query mode: simple
number of clients: 40
number of transactions per client: 100
number of transactions actually processed: 4000/4000
tps =3D 1040.534002 (including connections establishing)
tps =3D 1065.215134 (excluding connections establishing)
Even optimizing the postgresql.conf values doesn't change a lot on the =
tps values. (less than 10%)
Tried Postgresql 9.1 on the Proliant:
transaction type: TPC-B (sort of)
scaling factor: 1
query mode: simple
number of clients: 40
number of threads: 1
number of transactions per client: 100
number of transactions actually processed: 4000/4000
tps =3D 53.114978 (including connections establishing)
tps =3D 53.198667 (excluding connections establishing)
Next was to compare the diskperformance which was much better on the =
XEON than on the Intel i7.
Any idea where to search for the bottleneck?
best regards,
Felix Schubert=