Message-ID: <53D30CEA.5080101@hogranch.com>
Date: Fri, 25 Jul 2014 19:05:30 -0700
From: John R Pierce <pierce@hogranch.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: Checkpoint_segments optimal value
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>
In-Reply-To: 
 <CAOf_bQaAx1uRH+GAMReYwOGWgOLgZJUyPabUS2V5-e_CB13Y=g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-general-owner@postgresql.org

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