> I wrote a rails app and looking back, I think a big piece of the > performance thing is in wise use of :include in object fetches (if you > do not use :include, then rails will never do joins and will always make > separate queries in each table). It's all too easy to code up something > that does no sql joins at all.
Well, that would be a big factor, but just regular Ruby code is interpreted very slowly compared to other similar languages. But the same could be said for Java when it was as old as Ruby. I imagine the same could be said for a lot of dynamic languages (note: I know Java is not dynamic, I'm referring to Perl, PHP, etc) in their early stages as well, but I am too young or unfamiliar with them to know. It'll likely get better over time. If not, Perl 6 might finally see the light of day, and from some accounts it is roughly twice as fast as Perl 5. And then Python programmers will still bash it, and Perl programmers won't care what Python programmers think, and the cycle will continue :) Greg /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
