OnMetal: The Right Way To Scale

Re:OnMetal: The Right Way To Scale by Serow225 on Thursday June 19, 2014 @09:35PM (#7919140)

Kudos, very cool. Maybe instead of 'no disk' something like 'SSD for boot media, no local bulk storage' would be clearer, as I was a little confused by this as other posters below were. It's also a little interesting that the 'High CPU' option has the fewest cores of the three options... Any comments on that?

[ Parent | on HN ]

Re:OnMetal: The Right Way To Scale by vehementi on Thursday June 19, 2014 @10:41PM (#7919309)

It's low on other resources so it's probably lowest cost per CPU.

[ Parent | on HN ]

Re:OnMetal: The Right Way To Scale by russell_h on Friday June 20, 2014 @01:01PM (#7921580)

That's basically correct, we were trying to balance a few factors:

  - Total cost
  - Cost per core
  - Clock speed (this actually matters a lot for, say, a Python webapp)

We chose to run only a single CPU in this box to keep the total cost of the box low. This slightly increase the cost per core (switch ports, the chassis, rack space, etc being basically fixed overhead per node), but by selling in smaller increments we think it we can keep the total cost lower for most users.

We'll be gathering feedback on the resource balance, and iterating as we go.

[ Parent | on HN ]