Get two free computers for a year!

[chalsall]

Hey all... I'm not sure if this is a good idea or not. But what the heck...

I'm at the stage with my project where I need some BIG iron. But only occasionally. I decided it was time to start learning how to leverage Amazon's EC2.

I went to sign up, and discovered that for new customers they're offering a year's worth of "t1.micro" Linux instances AND a year's worth of Windows instances for free! All you need is a valid credit card -- they won't bill it unless you have "overage".

Details are at http://aws.amazon.com/free/faqs/.

The virtual machine provided isn't too powerful (and its performance jumps around a bit, as one would expect), but it's definitely not a 386 either... And it's free!

[Work thread Feb 3 18:50] Timing 44 iterations of 768K FFT length.  Best time: 13.440 ms., avg time: 17.524 ms.
[Work thread Feb 3 18:50] Timing 38 iterations of 896K FFT length.  Best time: 16.233 ms., avg time: 19.454 ms.
[Work thread Feb 3 18:50] Timing 33 iterations of 1024K FFT length.  Best time: 18.026 ms., avg time: 22.605 ms.
[Work thread Feb 3 18:51] Timing 26 iterations of 1280K FFT length.  Best time: 28.171 ms., avg time: 31.836 ms.
[Work thread Feb 3 18:51] Timing 22 iterations of 1536K FFT length.  Best time: 32.071 ms., avg time: 34.310 ms.
[Work thread Feb 3 18:51] Timing 19 iterations of 1792K FFT length.  Best time: 37.485 ms., avg time: 40.224 ms.
[Work thread Feb 3 18:51] Timing 16 iterations of 2048K FFT length.  Best time: 43.034 ms., avg time: 44.666 ms.
[Work thread Feb 3 18:51] Timing 13 iterations of 2560K FFT length.  Best time: 52.075 ms., avg time: 55.121 ms.
[Work thread Feb 3 18:51] Timing 11 iterations of 3072K FFT length.  Best time: 66.438 ms., avg time: 74.521 ms.
[Work thread Feb 3 18:51] Timing 10 iterations of 3584K FFT length.  Best time: 92.998 ms., avg time: 108.097 ms.
[Work thread Feb 3 18:51] Timing 10 iterations of 4096K FFT length.  Best time: 924.122 ms., avg time: 1065.588 ms.
[Work thread Feb 3 18:52] Timing 10 iterations of 5120K FFT length.  Best time: 117.753 ms., avg time: 136.621 ms.
[Work thread Feb 3 18:54] Timing 10 iterations of 6144K FFT length.  Best time: 141.004 ms., avg time: 146.417 ms.
[Work thread Feb 3 18:55] Timing 10 iterations of 7168K FFT length.  Best time: 162.681 ms., avg time: 256.381 ms.
[Work thread Feb 3 18:56] Timing 10 iterations of 8192K FFT length.  Best time: 1858.992 ms., avg time: 1979.887 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 61 bit length factors.  Best time: 4.001 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 62 bit length factors.  Best time: 4.017 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 63 bit length factors.  Best time: 7.024 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 64 bit length factors.  Best time: 6.895 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 65 bit length factors.  Best time: 6.189 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 66 bit length factors.  Best time: 6.210 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 67 bit length factors.  Best time: 6.109 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 75 bit length factors.  Best time: 6.565 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 76 bit length factors.  Best time: 6.493 ms.
[Work thread Feb 3 18:56] Timing trial factoring of M35000011 with 77 bit length factors.  Best time: 6.500 ms.

Certainly enough to clear a few DCs, LLs or P-1s in a year....

[kracker]

Very interesting. Thanks!

[dabaichi]

It's awesome! Thanks for sharing!

[Batalov]

CPU Information:
Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz
CPU speed: 2659.55 MHz
CPU features: Prefetch, SSE, SSE2, SSE4
L1 cache size: 32 KB
L2 cache size: 6 MB

Almost identical values in benchmark.
Fairly nice (even if a bit old, this series was launched in 2007), and, indeed, free!

We don't look a Trojan horse in the mouth, do we?

[TObject]

750 hours is just a little over a month. Or am I reading it wrong?

But, thanks for sharing in any way. Nice find.

[chalsall]

Originally Posted by TObject

750 hours is just a little over a month. Or am I reading it wrong?]

24 * 31 == 744.

[TObject]

Originally Posted by chalsall

24 * 31 == 744.

I mean, it is not anywhere close to a year; only 750 hours are free. Or not?

[chalsall]

Originally Posted by TObject

I mean, it is not anywhere close to a year; only 750 hours are free. Or not?

You didn't read the Terms...

You get 750 hours per month for a year.

Sadly, it appears English is as scary as Math.

Just introduce Latin, and the masses will be running scared towards to the Super Bowl....

[TObject]

Originally Posted by chalsall

You didn't read the Terms...

You get 750 hours per month for a year.

Sadly, it appears English is as scary as Math.

Just introduce Latin, and the masses will be running scared towards to the Super Bowl....

Thank you for answering my question. The terms, as posted on the amazon web site, were unclear to me.

[Uncwilly]

[TObject]

Now the physics question: how fast does the server need to move relative to the observer so that the when the observer counts 744 hours on his or her watch, 750 hours had passed on the server. LOL