[EMAIL PROTECTED] (Joshua D. Drake) wrote in pgsql.performance:
Jeff wrote:
On Dec 23, 2004, at 9:27 AM, Alex wrote:
Running hdparm reported
A) 920mb/s (SCSI 10k)
B) 270mb/s (SCSI 10k)
C) 1750mb/s (IDE 7.2k)
IDE disks lie about write completion (This can be disabled on some
Hi,
i recently run pgbench against different servers and got some results I
dont quite understand.
A) EV1: Dual Xenon, 2GHz, 1GB Memory, SCSI 10Krpm, RHE3
B) Dual Pentium3 1.4ghz (Blade), SCSI Disk 10Krmp, 1GB Memory, Redhat 8
C) P4 3.2GHz, IDE 7.2Krpm, 1GBMem, Fedora Core2
All did run only
On Dec 23, 2004, at 9:27 AM, Alex wrote:
Running hdparm reported
A) 920mb/s (SCSI 10k)
B) 270mb/s (SCSI 10k)
C) 1750mb/s (IDE 7.2k)
IDE disks lie about write completion (This can be disabled on some
drives) whereas SCSI drives wait for the data to actually be written
before they report
Alex wrote:
Hi,
i recently run pgbench against different servers and got some results I
dont quite understand.
A) EV1: Dual Xenon, 2GHz, 1GB Memory, SCSI 10Krpm, RHE3
B) Dual Pentium3 1.4ghz (Blade), SCSI Disk 10Krmp, 1GB Memory, Redhat 8
C) P4 3.2GHz, IDE 7.2Krpm, 1GBMem, Fedora Core2
Runnig
IDE disks lie about write completion (This can be disabled on some
drives) whereas SCSI drives wait for the data to actually be written
before they report success. It is quite
easy to corrupt a PG (Or most any db really) on an IDE drive. Check
the archives for more info.
Do we have any real
