Thanks Yves for the clarification!
It used to be very important to pre-warm EBS before running benchmarks
in order to get consistent results.
Then at re:Invent 2015, the AWS engineers said that it is not needed
anymore, which IMO is a lot less work for us to do benchmarking in
AWS, because
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
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,
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/
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
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
>
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.
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
Yes, the smaller instance you choose - the slower ebs will be.
EBS lives separately from EC2, they are communicating via network. So small
instance = low network bandwidth = poorer disk performance.
But still strong recommendation to pre-warm your ebs in any case,
especially if they created from
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
--
Hi.
AWS EBS its a really painful story
How was created volumes for RAID? From snapshots?
If you want to get the best performance from EBS it needs to pre-warmed.
Here is the tutorial how to achieve that:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html
Also you should
Actually, when "EBS-Optimized" is on, then the instance gets dedicated
bandwidth to EBS.
Rayson
==
Open Grid Scheduler - The Official Open Source Grid Engine
http://gridscheduler.sourceforge.net/
Indeed, old-style disk EBS vs new-style SSd EBS.
Be aware that EBS traffic is considered as part of the total "network"
traffic, and each type of instance has different limits on maximum network
throughput. Those difference are very significant, do tests on the same volume
between two different
There are many factors that can affect EBS performance. For example, the
type of EBS volume, the instance type, whether EBS-optimized is turned on
or not, etc.
Without the details, then there is no apples to apples comparsion...
Rayson
==
Open
14 matches
Mail list logo