Re: Postgresql Performance on an HP DL385 and - Mailing list pgsql-performance

From Luke Lonergan
Subject Re: Postgresql Performance on an HP DL385 and
Date
Msg-id 3E37B936B592014B978C4415F90D662D03FFEF6E@MI8NYCMAIL06.Mi8.com
Whole thread Raw
Responses Re: Postgresql Performance on an HP DL385 and  ("Steve Poe" <steve.poe@gmail.com>)
List pgsql-performance
Steve,

> Sun box with 4-disc array (4GB RAM. 4 167GB 10K SCSI RAID10
> LSI MegaRAID 128MB). This is after 8 runs.
>
> dbserver-dual-opteron-centos,08/08/06,Tuesday,20,us,12,2,5
> dbserver-dual-opteron-centos,08/08/06,Tuesday,20,sy,59,50,53
> dbserver-dual-opteron-centos,08/08/06,Tuesday,20,wa,1,0,0
> dbserver-dual-opteron-centos,08/08/06,Tuesday,20,id,45,26,38
>
> Average TPS is 75
>
> HP box with 8GB RAM. six disc array RAID10 on SmartArray 642
> with 192MB RAM. After 8 runs, I see:
>
> intown-vetstar-amd64,08/09/06,Tuesday,23,us,31,0,3
> intown-vetstar-amd64,08/09/06,Tuesday,23,sy,16,0,1
> intown-vetstar-amd64,08/09/06,Tuesday,23,wa,99,6,50
> intown-vetstar-amd64,08/09/06,Tuesday,23,id,78,0,42
>
> Average TPS is 31.

Note that the I/O wait (wa) on the HP box high, low and average are all
*much* higher than on the Sun box.  The average I/O wait was 50% of one
CPU, which is huge.  By comparison there was virtually no I/O wait on
the Sun machine.

This is indicating that your HP machine is indeed I/O bound and
furthermore is tying up a PG process waiting for the disk to return.

- Luke


pgsql-performance by date:

Previous
From: Steve Poe
Date:
Subject: Re: Postgresql Performance on an HP DL385 and
Next
From: "Luke Lonergan"
Date:
Subject: Re: Postgresql Performance on an HP DL385 and