<div dir="ltr"><div class="gmail_quote">On Sun, Oct 10, 2010 at 5:04 PM, Orna Agmon Ben-Yehuda <span dir="ltr"><<a href="mailto:ladypine@gmail.com">ladypine@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr"><br><br><div class="gmail_quote"><div class="im">2010/10/10 Ori Idan <span dir="ltr"><<a href="mailto:ori@helicontech.co.il" target="_blank">ori@helicontech.co.il</a>></span><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br><div class="im"><div class="gmail_quote">2010/10/10 Tom Rosenfeld <span dir="ltr"><<a href="mailto:trosenfeld@gmail.com" target="_blank">trosenfeld@gmail.com</a>></span><div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi,<br>I just came across this thread from back in Aug about Amazon's cloud.<br>
<br>I'd like to add that I have been a satisfied customer of Amazon for over a year, using their services for both consulting at at my current job where we use it to run our SaaS offering. The capabilities keep improving and the prices keep coming down. Their lowest end server is now just 2 cents an hour!<br>
<br>There are some issues with the IO, but it is certainly adequate for all but high performance needs. We use 8 way stripped disks and get about 100 MBp/s sequential reads. <br><br>If anyone wants more details, I'll be happy to share with you.<br>
<br>-tom<br><br></div></blockquote><div><br></div></div><div>I am considering using EC2 for a web application.</div><div>I am not sure how to calculate the payment per month.</div><div>Do I pay only for the time someone makes a request?</div>
<div>For example, I have a user who requests a certain report and it takes 1 second to load the report request form, then 20 seconds to produce the report and print it.</div><div>I understand that I pay for 21 seconds?</div>
</div></div></div></blockquote><div><br></div><div>In addition to mistakes already corrected, there is another mistake of how long something takes. Amazon aim to provide a certain computation power unit, but benchmarks show that what is actually provided has high variability. For example, ping times to EC2 machines started rising significantly since Amazon announces the spot instances. See also:</div>
<div><br></div></div></div></blockquote><div><br></div><div><br></div><div>Some more input on EC2.</div><div><br></div><div>Not all instances born alike. We recently ran a huge computation based on Hadoop and you can definitely see that some nodes perform faster (I/O was the bottleneck) then others.</div>
<div><br></div><div>I too, when starting with EC2 made the mistake to of thinking that you only pay for as much "CPU" as you use. Wrong! </div><div><br></div><div>OTOH, I was very happy to find out that with Google AppEngine this is actually the case: You pay for as much resources as you consume. And they DO count "CPU Time" vs. Amazon's "instance is running time".</div>
<div><br></div><div>Another note regarding EC2. Read bitbucket story about ec2 horrors <a href="http://blog.bitbucket.org/">http://blog.bitbucket.org/</a>.</div><div>Yet please don't get me wrong, generally EC2, S3, CloudFront, ELB and other Amazon's services work great - Our production farm (~40 servers is hosted there and we are relatively happy).</div>
<div><br></div><div>Amazon's main issues are: </div><div>I/O bandwidth is funny</div><div>Occasionally peaks in connectivity time that lead to timeouts (between zones & from the outside world).</div><div>Not so fair hypervisor: We've seen occasions when an instance "slows down" for a couple of minutes. We assume (without being able to tell for sure) that some bigger instance type that happen to be hosted on the same physical server as we are got resource hungry and practically ate all our CPU time...</div>
<div><br></div><div><br></div><div>Maxim.</div></div><br></div>