From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Chris Barnes <compuguruchrisbarnes(at)hotmail(dot)com> |
Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Raid 10 settings for optimal postgres performance? |
Date: | 2010-03-03 21:08:39 |
Message-ID: | 4B8ECFD7.6000508@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Chris Barnes wrote:
> What is the preferred setup for postgres concerning cache settings on
> the controller and disks and the preferred block size allocated for
> the disks when postgres uses block size 8192?
>
> Controller settings
> Read-cache mode - Enabled
> Write-cache mode - Enabled (write-back)
> Write-cache setting - Enabled (write-back) when protected by battery
> Stripe-unit size : 256 KB
>
> Disk setting
> Write Cache : Disabled (write-through)
You already have the right cache settings: write-back when protected by
battery, write cache on disks disabled. And there aren't any
interesting settings to change for block of stripe size on a RAID10
array that do anything you'll be able to measure. You're done with
controller and disk setup.
Looks like a standard ext3 filesystem under Linux, right? Next you
should run tests with bonnie++ to make sure the array is performing as
expecting.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-03-03 21:24:25 | Re: Larger volumes of chronologically ordered data and the planner |
Previous Message | Greg Sabino Mullane | 2010-03-03 21:07:13 | Re: PQntuples returns an int. |