I might suggest that there's some irony in suggesting that one use Ruby to write an algorithm that's going to basically be 100% compute bound . . . seems like this contest is a classic example of exactly the sort of problem where you do, in fact, care about raw language performance.