frehpt

It's only drastically slower because the micro instance gets very heavily throttled when you put it under sustained load. If you use it for what it's designed for the performance is much better as you don't get throttled with light usage. The benchmark is of the slowest ec2 instance type while being heavily throttled due to the benchmark generating too much load.

I don't see how that proves anything. They're using an old first generation instance type and benchmarking it alongside a much more powerful i7 processor. If you want a faster instance get a second generation instance or a larger one.

I think you're missing the point of the micro instance. It can give you decent performance in short bursts, which is suitable for many light usage cases e.g. a low traffic blog. If you are going to load it via a benchmark you get very heavily throttled way below the performance you would get with light usage.

Incorrect, Amazon.com runs on AWS: https://news.ycombinator.com/item?id=5588012

Is that the sound of the power supply going on your Pentium 3...

...or your internet connection

You never patch or reboot your magic box either?

Exactly...

> Go does't have 1/100000 the amount of libraries and support that Ruby or C does.

That's what they used to say about Java...

Option A:

  -Write your application in Go

Option B:

  -Write application in Ruby
  -Profile Ruby application to identify code to be rewritten in C
  -Learn C if you don't already know it
  -Rewrite various parts of your application in C
  -Run Valgrind to search for memleaks
  -Ensure that your target systems all have required libs installed

Option A seems much simpler...