AFAIK the EC2 service charges a flat rate for the time that your instance is running, regardless of the workload or lack thereof. My understanding would be the charge is $0.02/hr, without any exceptions. It sounds like they will throttle the cpu cycles if your workload consumes them too fast for an extended period of time. So rather than an instantaneous cpu cap, there's some cap on the average over some period of time. I haven't searched for any details yet.<br>
<br>Kendall<br><br><br><div class="gmail_quote">On Thu, Sep 9, 2010 at 9:11 AM, L. V. Lammert <span dir="ltr"><<a href="mailto:lvl@omnitec.net">lvl@omnitec.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">At 08:48 AM 9/9/2010, you wrote:<br>
>EC2 has been a very cheap way to experiment with servers in the past<br>
>at $0.075 per hour but that ran to $54/mo if you used it full time.<br>
>This new instance brings the price down to $14 /mo for a full time<br>
>instance which puts it into the same ballpark as a linode ($20/mo but<br>
>not an apples to apples comparison).<br>
<br>
</div>Any feel of how the 'per hour' translates to actual usage? For<br>
example, does the cost structure actually product no charge when a<br>
web site is not getting page request? Does a system ever use *more*<br>
than the .02/hr?<br>
<br>
Lee<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</div></div></blockquote></div><br>