Message-ID: <51C366CE.10206@agliodbs.com>
Date: Thu, 20 Jun 2013 13:32:14 -0700
From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL Experts Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
CC: Greg Smith <greg@2ndQuadrant.com>
Subject: Re: PostgreSQL settings for running on an SSD drive
References: <51C35E6C.1090705@consistentstate.com>
 <51C36256.6040502@optionshouse.com>
 <WM!b9e5afbe8d527efb5c0f49ce7515ef211125a953db249e1e3ff58e04ad0791f3381fd39085635a2bb537ff66f740d4f2!@asav-1.01.com>
In-Reply-To: 
 <WM!b9e5afbe8d527efb5c0f49ce7515ef211125a953db249e1e3ff58e04ad0791f3381fd39085635a2bb537ff66f740d4f2!@asav-1.01.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Folks,

First, cc'ing Greg Smith to see if he can address this with the Fusion
folks so that they stop giving out a bad guide.

On 06/20/2013 01:13 PM, Shaun Thomas wrote:
> On 06/20/2013 02:56 PM, CS DBA wrote:
>=20
>> They have a PostgreSQL setup guide from Fusion recommending the
>> following settings:
>> effective_io_concurrency=3D0
>> bgwriter_lru_maxpages=3D0
>> random_page_cost=3D0.1
>> sequential_page_cost=3D0.1=E2=80=A8
>=20
> Well, since FusionIO drives have a limited write cycle (5PB?), I can
> somewhat see why they would recommend turning off the background writer.
> We were a bit more conservative in our settings, though:
>=20
> seq_page_cost =3D 1.0      # Default
> random_page_cost =3D 1.0   # Reduce to match seq_page_cost
>=20
> Yep. That's it. Just the one setting. FusionIO drives are fast, but
> they're not infinitely fast. My tests (and others) show they're about
> 1/2 the speed of memory, regarding IOPS. And while they can serve very
> aggressive sequential reads, they're not orders of magnitude faster than
> spindles in anything but IOPS.
>=20
> Knowing that, we reduced random page fetches to be the same speed as
> sequential page fetches. This has served our heavy OLTP system (and its
> FusionIO underpinnings) very well so far.

Did you compare setting RPC to 1.0 vs. setting it to 1.1, or something
else just slightly higher than SPC?

--=20
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


--=20
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance