News for hackers. Stuff that matters.
Re:Rackspace vs. EC2: Performance Analysis by allertonm on Monday January 11, 2010 @04:27PM (#1046060)
Compiling the linux kernel seems like a poor choice of test, since it is not a pure CPU activity and will perform a significant amount of I/O.

In addition, it doesn't seem like compiling the linux kernel requires very much RAM, so you get the most bang for your buck using a CS VM with only 256MB and the cost only goes up from there as you add more RAM that the test cannot benefit from.

(Edit: I would love whoever downmodded me to explain why I am wrong.)

Re:Rackspace vs. EC2: Performance Analysis by pquerna on Monday January 11, 2010 @04:35PM (#1046087)
its a decent enough test, mostly because most geeks out there have done it themselves, so you can get a good 'feel' for a machine by knowing how long it takes to compile the kernel.

its not perfect, and yeah, its kinda a geeky-benchmark, but it doesn't make it an invalid benchmark, as long as it was conducted correctly.

Re:Rackspace vs. EC2: Performance Analysis by allertonm on Monday January 11, 2010 @04:45PM (#1046105)
I consider myself a geek (and most of my friends would agree) but it's been 15 years since I last compiled the Linux kernel :)

That said, I wouldn't rule it out as a test because of that, but I do think that if you are going to compare 4 different RAM sizes of CS instances, and compare the costs of doing a job using those different sizes then you need to pick a job that is going to make use of the RAM. You can see from the results that there is a small (time) benefit moving from 256 to 512MB (but not enough to offset the increased costs) and virtually none above that.