Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b5wpV-000410-Mh for pgsql-performance@arkaria.postgresql.org; Thu, 26 May 2016 15:04:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b5wpU-0006aA-NE for pgsql-performance@arkaria.postgresql.org; Thu, 26 May 2016 15:04:08 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b5wpT-0006XY-KZ for pgsql-performance@postgresql.org; Thu, 26 May 2016 15:04:07 +0000 Received: from mail-lf0-x231.google.com ([2a00:1450:4010:c07::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1b5wpM-0005Vd-4L for pgsql-performance@postgresql.org; Thu, 26 May 2016 15:04:06 +0000 Received: by mail-lf0-x231.google.com with SMTP id w16so21628727lfd.2 for ; Thu, 26 May 2016 08:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leboutique.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0Ys8zCPfS/w8F8YoV0XZ6fljIAgvxezNzAouLPRqEm8=; b=Wdzvq5NQXQ0yR7ebqR5GeG1iWpd1CCm9jB8uP6wCja9i6zwtU2+PfpUrvPCQAxttqE cN8HvHQuLLG0R0NerZAVKHUw5vZdwMMGicPySYJU0clqH6SF7KMfqs7AWZC8RG+ED8eD zm/vLgykZFExM6amj5ArI8tseE4N6eQEaHYmA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0Ys8zCPfS/w8F8YoV0XZ6fljIAgvxezNzAouLPRqEm8=; b=iGFn/qpyc20b1wvtQZ35/WmOCcCi3ZDUPeO9oEzitHkw0X02OSCfV0qB6tcfklAt+P nKHhNXMiKcKYnt0+3d0Uq4gTHppXrTYrs1f7EOOOPixszq+g3uJ7iXzADIedZcvo0CC4 md4FTvkblL9VVPVPFrA3E6XqrekrP+ZbYxVJzN/oo+v+zxVqDA6ChvfEGwpvAVvaNy7k lwQZ4dwg7PQO+98eUrrMDZWGJCJ1HKAV+RISbQB68jskMB+Kp2Be/uY9Ut6A9jPKe+1C wJA908rspkCMdp4kIkR3Bw1+dC+wrP4nzgKmnbmY5lqUPWseVPERJVugWGKEstQu/Eme bhlw== X-Gm-Message-State: ALyK8tJ6KMH7nZf9JwYyDEVbbgn4hCnsaMQTYs5yFPdVURqbic1hRDaai5cVeBP2TI6XC2+Nhx+t7IacCWFEBEl+ X-Received: by 10.25.17.105 with SMTP id g102mr3232778lfi.145.1464275038002; Thu, 26 May 2016 08:03:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.18.229 with HTTP; Thu, 26 May 2016 08:03:38 -0700 (PDT) In-Reply-To: References: <57463BAC.2090608@zioup.com> <5746F1B3.8080701@zioup.com> From: Artem Tomyuk Date: Thu, 26 May 2016 18:03:38 +0300 Message-ID: Subject: Re: Testing in AWS, EBS To: Rayson Ho Cc: Yves Dorfsman , pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=001a113fbbf87e727b0533c019d0 X-Pg-Spam-Score: -2.7 (--) 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 --001a113fbbf87e727b0533c019d0 Content-Type: text/plain; charset=UTF-8 Why no? Or you missed something? It should be done on every EBS restored from snapshot. Is that from your personal experience, and if so, when did you do the test?? Yes we are using this practice, because as a part of our production load we are using auto scale groups to create new instances, wheech are created from AMI, wheech stands on snapshots, so... 2016-05-26 17:54 GMT+03:00 Rayson Ho : > Thanks Artem. > > So no EBS pre-warming does not apply to EBS volumes created from snapshots. > > Rayson > > ================================================== > Open Grid Scheduler - The Official Open Source Grid Engine > http://gridscheduler.sourceforge.net/ > http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > > > On Thu, May 26, 2016 at 10:52 AM, Artem Tomyuk > wrote: > > Please look at the official doc. > > > > "New EBS volumes receive their maximum performance the moment that they > are > > available and do not require initialization (formerly known as > pre-warming). > > However, storage blocks on volumes that were restored from snapshots > must be > > initialized (pulled down from Amazon S3 and written to the volume) before > > you can access the block" > > > > Quotation from: > > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html > > > > 2016-05-26 17:47 GMT+03:00 Rayson Ho : > >> > >> On Thu, May 26, 2016 at 10:00 AM, Artem Tomyuk > >> wrote: > >>> > >>> > >>> 2016-05-26 16:50 GMT+03:00 Rayson Ho : > >>>> > >>>> Amazon engineers said that EBS pre-warming is not needed anymore. > >>> > >>> > >>> but still if you will skip this step you wont get much performance on > ebs > >>> created from snapshot. > >> > >> > >> > >> IIRC, that's not what Amazon engineers said. Is that from your personal > >> experience, and if so, when did you do the test?? > >> > >> Rayson > >> > >> ================================================== > >> Open Grid Scheduler - The Official Open Source Grid Engine > >> http://gridscheduler.sourceforge.net/ > >> http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > >> > >> > >> > > > --001a113fbbf87e727b0533c019d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Why no? Or you missed something?

It should be= done on every EBS restored from snapshot.=C2=A0

=
Is that from your personal experience= , and if so, when did you do the test??

Y= es we are using this practice, because as a part of our production load we = are using auto scale groups to create new instances, wheech are created fro= m AMI, wheech stands on snapshots, so...=C2=A0

<= div>


<= span style=3D"font-size:12.8px">=C2=A0


2016-05-26 17:54 GMT+03:00 Rayson Ho <raysonlogin@gmail.= com>:
Thanks Artem.

So no EBS pre-warming does not apply to EBS volumes created from snapshots.=

Rayson

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
Open Grid Scheduler - The Official Open Source Grid Engine
http://gridscheduler.sourceforge.net/
http://gridscheduler.sourceforge= .net/GridEngine/GridEngineCloud.html


On Thu, May 26, 2016 at 10:52 AM, Artem Tomyuk <admin@leboutique.com= > wrote:
> Please look at the official doc.
>
> "New EBS volumes receive their maximum performance the moment tha= t they are
> available and do not require initialization (formerly known as pre-war= ming).
> However, storage blocks on volumes that were restored from snapshots m= ust be
> initialized (pulled down from Amazon S3 and written to the volume) bef= ore
> you can access the block"
>
> Quotation from:
> http://docs.aws.amazon.co= m/AWSEC2/latest/UserGuide/ebs-initialize.html
>
> 2016-05-26 17:47 GMT+03:00 Rayson Ho <raysonlogin@gmail.com>:
>>
>> On Thu, May 26, 2016 at 10:00 AM, Artem Tomyuk <admin@leboutique.com>
>> wrote:
>>>
>>>
>>> 2016-05-26 16:50 GMT+03:00 Rayson Ho <raysonlogin@gmail.com>:
>>>>
>>>> Amazon engineers said that EBS pre-warming is not needed a= nymore.
>>>
>>>
>>> but still if you will skip this step you wont get much perform= ance on ebs
>>> created from snapshot.
>>
>>
>>
>> IIRC, that's not what Amazon engineers said. Is that from your= personal
>> experience, and if so, when did you do the test??
>>
>> Rayson
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D
>> Open Grid Scheduler - The Official Open Source Grid Engine
>> http://gridscheduler.sourceforge.net/
>> http://gridscheduler.so= urceforge.net/GridEngine/GridEngineCloud.html
>>
>>
>>
>

--001a113fbbf87e727b0533c019d0--