From: | Rayson Ho <raysonlogin(at)gmail(dot)com> |
---|---|
To: | Artem Tomyuk <admin(at)leboutique(dot)com> |
Cc: | Yves Dorfsman <yves(at)zioup(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Testing in AWS, EBS |
Date: | 2016-05-26 13:50:23 |
Message-ID: | CAHwLALNZZ_KU7eAcfar9-k_tKzkQwkU-dHQPhcPYM6_X8V6uSQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, May 26, 2016 at 9:00 AM, Artem Tomyuk <admin(at)leboutique(dot)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. 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 <yves(at)zioup(dot)com>:
>>
>> 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(at)postgresql(dot)org
)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-performance
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Artem Tomyuk | 2016-05-26 14:00:26 | Re: Testing in AWS, EBS |
Previous Message | Artem Tomyuk | 2016-05-26 13:00:23 | Re: Testing in AWS, EBS |