From: John R Pierce <pierce@hogranch.com>
To: pgsql-general@postgresql.org
Subject: Re: Checkpoint_segments optimal value
Date: Fri, 25 Jul 2014 19:05:30 -0700
Message-ID: <53D30CEA.5080101@hogranch.com> (raw)
In-Reply-To: <CAOf_bQaAx1uRH+GAMReYwOGWgOLgZJUyPabUS2V5-e_CB13Y=g@mail.gmail.com>
References: <CAOf_bQYehfKp7CNRa_pYQ+-SmHyDSYJ8bddbaixXUcWmSjH6wA@mail.gmail.com>
<1405975881.98993.YahooMailNeo@web122303.mail.ne1.yahoo.com>
<53CD8048.4010002@hogranch.com>
<CAOf_bQaAx1uRH+GAMReYwOGWgOLgZJUyPabUS2V5-e_CB13Y=g@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
On 7/25/2014 5:58 PM, Prabhjot Sheena wrote:
> We do have i/o problem during heavy loads because we share mount point
> from netapp across different machines which we are getting rid in few
> weeks by moving stuff to Amazon aws and than IO issues will go away
> with fast iops
Netapp has to be some of the most expensive storage I've ever seen in a
datacenter and is frequently a source of performance problems. NFS
isn't really appropriate for storing database data on, there's way too
many opportunites for fsync to get lost, more so if you've got a
virtualization layer in there too.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pierce@hogranch.com, pgsql-general@postgresql.org
Subject: Re: Checkpoint_segments optimal value
In-Reply-To: <53D30CEA.5080101@hogranch.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox