Ruby Fibonacci Shootout
christopherroach.com
Ruby Fibonacci Shootout
1–10 of 15 posts
Re: Ruby Fibonacci Shootout
#2Based on this article, I would totally consider moving to Ruby for my Fibonacci number needs.
Re: Ruby Fibonacci Shootout
#3I don't think this "CPU Intensive" task is the kind of CPU-intensive task you actually care about. I haven't done any formal experimentation, but I'm guessing this is a better test of how many instructions are generated for a call/ret sequence, and not how well normal CPU-intensive operations would work. I would think some code that did a fair amount of number crunching/lookups in a tight loop would be a much better test.
But, then again, it doesn't really matter. Is Ruby fast enough to work for most uses? Yes. If you really, really, really care about execution speed, would you use Ruby? I don't know. If you care that much about execution speed, you will probably do more benchmarks than I care to think of.
Re: Ruby Fibonacci Shootout
#4Huh? Where's the results? Or are readers supposed to run the code and send their results or something? But there's no timing check in the code he posted anyway.
Re: Ruby Fibonacci Shootout
#5Huh? Where's the results? Or are readers supposed to run the code and send their results or something? But there's no timing check in the code he posted anyway.
They don't render in IE (tested in 8); it cuts the article in half.
Re: Ruby Fibonacci Shootout
#6Ported this to scala (I know, I didn't do this functionally, this is a pretty straight port of the C example), ran in 4 seconds (of course, I've got about a bajillion other apps open right now, so take this with a grain of salt):
object Main {
def fib(n : int) : int = {
if(n "+fib(i).toString)
}
}
}Re: Ruby Fibonacci Shootout
#7I kept staring at this page, and yet despite its brevity, I could not find the results.
Apparently Firefox doesn't like the self-closing script tag?
Re: Ruby Fibonacci Shootout
#8Huh? Where's the results? Or are readers supposed to run the code and send their results or something? But there's no timing check in the code he posted anyway.
They don't render in IE (tested in 8); it cuts the article in half.
Or firefox mac. OK, now I looked at it through safari and I can see it.
Re: Ruby Fibonacci Shootout
#9I kept staring at this page, and yet despite its brevity, I could not find the results. Apparently Firefox doesn't like the self-closing script tag?
Is that valid? Also the script is missing the "type" attribute.
Re: Ruby Fibonacci Shootout
#10Recursive/iterative Fibonacci number generation is an interesting programming exercise but it's a bad example because in practice you'd be best to use an explicit constant-time formula.