Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b5xR8-0006KX-Do for pgsql-performance@arkaria.postgresql.org; Thu, 26 May 2016 15:43:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b5xR7-0007Z4-W0 for pgsql-performance@arkaria.postgresql.org; Thu, 26 May 2016 15:43:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b5xPS-0005i3-MY for pgsql-performance@postgresql.org; Thu, 26 May 2016 15:41:18 +0000 Received: from smtp-out-no.shaw.ca ([64.59.134.13]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b5xPN-0004Zk-VC for pgsql-performance@postgresql.org; Thu, 26 May 2016 15:41:17 +0000 Received: from home.zioup.com ([96.51.153.133]) by shaw.ca with SMTP id 5xPHb6nygUnqM5xPIbXY3I; Thu, 26 May 2016 09:41:09 -0600 X-Authority-Analysis: v=2.2 cv=bJxUG72Z c=1 sm=1 tr=0 a=pcwx/iW1S4GNAxS9KzaPFA==:117 a=pcwx/iW1S4GNAxS9KzaPFA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=yrkiwgmsf1kA:10 a=N8iSzGwtAAAA:8 a=dI4Q325bvXBQeJyA93EA:9 a=YHuoxGDvEISy2GqV2ok9:22 Received: from [192.168.246.243] (epicurus.zioup.net [192.168.246.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by home.zioup.com (Postfix) with ESMTPSA id 5CC4EA0330 for ; Thu, 26 May 2016 09:41:07 -0600 (MDT) Subject: Re: Testing in AWS, EBS To: pgsql-performance@postgresql.org References: <57463BAC.2090608@zioup.com> <5746F1B3.8080701@zioup.com> From: Yves Dorfsman Message-ID: <57471912.8050509@zioup.com> Date: Thu, 26 May 2016 09:41:06 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfNW3eYsH7iVAzHr/zXg3hShN8esIDr2EQmu/Z0pOQTSmKxuAHKfusWwZCh4oFfjVisXLud6EpX7RcK9I9LhjOt0tXZyH589ExHiMzkqF2f9s9FJ7yB2P aguI8y85hGS8ow1tgTxAGPhr95iHPn5XlhQPo4cMNHsLVwRwPoAdA5lW1Q2Ste5BtjFDw5VUf0TLDA== X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 2016-05-26 09:03, Artem Tomyuk wrote: > Why no? Or you missed something? I think Rayson is correct, but the double negative makes it hard to read: "So no EBS pre-warming does not apply to EBS volumes created from snapshots." Which I interpret as: So, "no EBS pre-warming", does not apply to EBS volumes created from snapshots. Which is correct, you sitll have to warm your EBS when created from sanpshots (to get the data from S3 to the filesystem). -- http://yves.zioup.com gpg: 4096R/32B0F416 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance