Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b5vhy-0002xc-RF for pgsql-performance@arkaria.postgresql.org; Thu, 26 May 2016 13:52:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b5vhx-0003DV-TX for pgsql-performance@arkaria.postgresql.org; Thu, 26 May 2016 13:52:17 +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 1b5vgH-0007vM-GB for pgsql-performance@postgresql.org; Thu, 26 May 2016 13:50:33 +0000 Received: from mail-oi0-x233.google.com ([2607:f8b0:4003:c06::233]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1b5vg9-0000bX-M7 for pgsql-performance@postgresql.org; Thu, 26 May 2016 13:50:33 +0000 Received: by mail-oi0-x233.google.com with SMTP id k23so125058569oih.0 for ; Thu, 26 May 2016 06:50:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=0c9j/7YNMZI9mBf9uzV2QdNicUtXhB5g/m9YBINbK9Q=; b=AR1MMjLnJTJjabG9AaFwtFXrYlWsaPsUfFcYc5bzwWqmIVFEN1k9Poj3C8/LjyqKRd EvuEVH6WnBhNbcviVk7dMpPSyXnCyiCbbNvzCzmQDfMGJaGnq/f1IbD3q7TqDBIJOVF3 wC4sCfSa2oFmBUoGI82eP0zW9Z5Jp/W0b1cO08YzMFKtUCMqmgH3uw/F5UQbnJTiNSiu PRKH5S/YUnTuc4c21Cz6IyxKD3jxxIaOepgu0duViBn/e5k9E7VcOo4vsmOlQjwU44Sy xPNSe23Oue296o8FDzxVkGJjjgdRBV7SYouHqFWnzbwJ0544cRKQqKgIUIgyyy2t2aEg Gu6A== 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:date :message-id:subject:from:to:cc; bh=0c9j/7YNMZI9mBf9uzV2QdNicUtXhB5g/m9YBINbK9Q=; b=ToCJYDieZnV6xa2mFEWH2KmzdXBXTc/tNZOqMMAcBsppwtoyS9Om0c0RTe6dH6Izvo dWBF22BJ/6b/RtA4RxdTS8NDSAhuzKtwCAdMyEtvJJOTriHWN2g4g1lWq3ZlXxEQx7B7 Io/sng61uQOnCres4yHc03rbN/uUXBCkaiyosPxqxkplQGBed18kjoMl0LeuvmLFwtWP ExpcbGp652L5CCrj6v2jt+moLuqzfVpfWMH7zMzarDHvVJpJs2AorOuI/ws5m4noYv1v p/IkFoL1zEwSQUkyUInCYuJ0REzV85lFUwI5shOW0h4v3dZY1a7pi49BAQSRgpUsu4FP h16g== X-Gm-Message-State: ALyK8tJ1m0BI4abH7WyUaD307FfaBxYWiPy53ZUsn2+S3EJlCHRl3btQ4C9hGOy5rN5Q9FM+NC1Do6OnMP/1WQ== MIME-Version: 1.0 X-Received: by 10.157.20.149 with SMTP id d21mr5802688ote.143.1464270623630; Thu, 26 May 2016 06:50:23 -0700 (PDT) Received: by 10.202.244.3 with HTTP; Thu, 26 May 2016 06:50:23 -0700 (PDT) In-Reply-To: References: <57463BAC.2090608@zioup.com> <5746F1B3.8080701@zioup.com> Date: Thu, 26 May 2016 09:50:23 -0400 Message-ID: Subject: Re: Testing in AWS, EBS From: Rayson Ho To: Artem Tomyuk Cc: Yves Dorfsman , pgsql-performance@postgresql.org Content-Type: multipart/alternative; boundary=001a113e22ac606eff0533bf1209 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 --001a113e22ac606eff0533bf1209 Content-Type: text/plain; charset=UTF-8 On Thu, May 26, 2016 at 9:00 AM, Artem Tomyuk wrote: > > But still strong recommendation to pre-warm your ebs in any case, especially if they created from snapshot. That used to be true. However, at AWS re:Invent 2015, Amazon engineers said that EBS pre-warming is not needed anymore. Rayson ================================================== Open Grid Scheduler - The Official Open Source Grid Engine http://gridscheduler.sourceforge.net/ http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html > 2016-05-26 15:53 GMT+03:00 Yves Dorfsman : >> >> On 2016-05-25 19:08, Rayson Ho wrote: >> > Actually, when "EBS-Optimized" is on, then the instance gets dedicated >> > bandwidth to EBS. >> >> Hadn't realised that, thanks. >> Is the EBS bandwidth then somewhat limited depending on the type of instance too? >> >> -- >> 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 > > --001a113e22ac606eff0533bf1209 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, May 26, 2016 at 9:00 AM, Artem Tomyuk <admin@leboutique.com> wrote:
>= ;
> But still strong recommendation to pre-warm your ebs in any case,= especially if they created from snapshot.

That used to be true. How= ever, at AWS re:Invent 2015, Amazon engineers said that EBS pre-warming is = not needed anymore.

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 Off= icial Open Source Grid Engine
http://gridscheduler.sourceforge.net/
http://gridsched= uler.sourceforge.net/GridEngine/GridEngineCloud.html



>= ; 2016-05-26 15:53 GMT+03:00 Yves Dorfsman <yves@zioup.com>:
>>
>> On 2016-05-25 19:08, = Rayson Ho wrote:
>> > Actually, when "EBS-Optimized" = is on, then the instance gets dedicated
>> > bandwidth to EBS.<= br>>>
>> Hadn't realised that, thanks.
>> Is th= e EBS bandwidth then somewhat limited depending on the type of instance too= ?
>>
>> --
>> = http://yves.zioup.com
>> gpg: 4096R/32B0F416
>>
&g= t;>
>>
>> --
>> Sent via pgsql-performance ma= iling list (pgsql-perfo= rmance@postgresql.org)
>> To make changes to your subscription= :
>> http://www.postgresql.org/mailpref/pgsql-performance
>
>= ;
--001a113e22ac606eff0533bf1209--