Slow Performance on a XEON E5504 - Mailing list pgsql-performance

From Felix Schubert
Subject Slow Performance on a XEON E5504
Date
Msg-id 63BD52D1-CE65-4A82-9071-E2ED44E2527F@fescon.de
Whole thread Raw
Responses Re: Slow Performance on a XEON E5504  (Marcos Ortiz <mlortiz@uci.cu>)
List pgsql-performance
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 = 158.283272 (including connections establishing)
tps = 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 = 1040.534002 (including connections establishing)
tps = 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 = 53.114978 (including connections establishing)
tps = 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?

Mit freundlichen Grüßen

Felix Schubert

FEScon
... and work flows!

felix schubert
haspelgasse 5
69117 heidelberg

mobil: +49-151-25337718
skype: fesmac

pgsql-performance by date:

Previous
From: Liron Shiri
Date:
Subject: Investigating the reason for a very big TOAST table size
Next
From: Liron Shiri
Date:
Subject: Investigating the reason for a very big TOAST table size