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@xxxxxxxxx> 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@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
