On Tue, Nov 10, 2009 at 4:48 PM, Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx> wrote: > Laurent Laborde <kerdezixe@xxxxxxxxx> wrote: > >> BTW, if you have any idea to improve IO performance, i'll happily >> read it. We're 100% IO bound. > > At the risk of stating the obvious, you want to make sure you have > high quality RAID adapters with large battery backed cache configured > to write-back. Not sure how "high quality" the 3ware is. /c0 Driver Version = 2.26.08.004-2.6.18 /c0 Model = 9690SA-8I /c0 Available Memory = 448MB /c0 Firmware Version = FH9X 4.04.00.002 /c0 Bios Version = BE9X 4.01.00.010 /c0 Boot Loader Version = BL9X 3.08.00.001 /c0 Serial Number = L340501A7360026 /c0 PCB Version = Rev 041 /c0 PCHIP Version = 2.00 /c0 ACHIP Version = 1501290C /c0 Controller Phys = 8 /c0 Connections = 8 of 128 /c0 Drives = 8 of 128 /c0 Units = 3 of 128 /c0 Active Drives = 8 of 128 /c0 Active Units = 3 of 32 /c0 Max Drives Per Unit = 32 /c0 Total Optimal Units = 2 /c0 Not Optimal Units = 1 /c0 Disk Spinup Policy = 1 /c0 Spinup Stagger Time Policy (sec) = 1 /c0 Auto-Carving Policy = off /c0 Auto-Carving Size = 2048 GB /c0 Auto-Rebuild Policy = on /c0 Controller Bus Type = PCIe /c0 Controller Bus Width = 8 lanes /c0 Controller Bus Speed = 2.5 Gbps/lane > If you haven't already done so, you might want to try > elevator=deadline. That's what we use. Also tried "noop" scheduler without signifiant performance change. -- ker2x -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
