<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>growt</author><text>Maybe I did something wrong with the setup but the disks (type gp2) are really slow compared with linode and digitalocean:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  ubuntu@aws:~$ dd bs=1M count=1024 if=&amp;#x2F;dev&amp;#x2F;zero of=test   conv=fdatasync
  1024+0 records in
  1024+0 records out
  1073741824 bytes (1.1 GB) copied, 23.1199 s, 46.4 MB&amp;#x2F;s
  ubuntu@aws:~$ sudo hdparm -tT &amp;#x2F;dev&amp;#x2F;disk&amp;#x2F;by-label&amp;#x2F;cloudimg-rootfs 

  &amp;#x2F;dev&amp;#x2F;disk&amp;#x2F;by-label&amp;#x2F;cloudimg-rootfs:
   Timing cached reads:   23292 MB in  1.99 seconds = 11704.62 MB&amp;#x2F;sec
   Timing buffered disk reads: 232 MB in  3.02 seconds =  76.70 MB&amp;#x2F;sec&lt;/code&gt;&lt;/pre&gt;</text><parent_chain></parent_chain></comment><story><title>Low Cost EC2 Instances With Burstable Performance</title><url>http://aws.amazon.com/blogs/aws/low-cost-burstable-ec2-instances/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jasonkester</author><text>Any thoughts on how this compares to simply spinning up a standard instance for a few hours then turning it off when you don&amp;#x27;t need it?&lt;p&gt;I run a service that needs to run about 72 hours worth of processing each day, and it all needs to happen during a 3 hour window.  That&amp;#x27;s a natural fit for spinning up a couple dozen instances then killing them when they finish.&lt;p&gt;I&amp;#x27;d love to see a comparison of what would happen if I kept the same amount of compute power on standby 24&amp;#x2F;7 using this new instance type.</text><parent_chain></parent_chain></comment><story><title>Low Cost EC2 Instances With Burstable Performance</title><url>http://aws.amazon.com/blogs/aws/low-cost-burstable-ec2-instances/</url></story>