Re: Testing in AWS, EBS

From: Rayson Ho <raysonlogin(at)gmail(dot)com>
To: Yves Dorfsman <yves(at)zioup(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Testing in AWS, EBS
Date: 2016-05-26 21:26:27
Message-ID: CAHwLALOdwg9WgoOW1mGb2=WZ+NORPkY+y4jaym2pNkN6tGz-5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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 pre-warming a multi-TB EBS vol is very time consuming,
and the I/Os were not free.

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 11:41 AM, Yves Dorfsman <yves(at)zioup(dot)com> wrote:
> 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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Johan Fredriksson 2016-05-27 12:10:30 Performance problems with 9.2.15
Previous Message Yves Dorfsman 2016-05-26 15:41:06 Re: Testing in AWS, EBS