On 3/9/07, Michael S. [email protected] wrote:
[1] http://dev.rubyonrails.org/ticket/2172
I’ve had this patch starred in my gmail ticket-box for so long, Michael.
Sorry I haven’t PDIed it up to edge yet 
jeremy
On Friday 09 March 2007, M. Edward (Ed) Borasky wrote:
I would think someone in the “core Rails team” would step up to the
plate for Rails-specific benchmarks. But if the specific case under
discussion here – ActiveRecord – turns out to have a bottleneck
somewhere in the Ruby interpreter, rather than just an inefficient
strategy in the ActiveRecord code itself, then I’d say this benchmark
belongs in a Ruby benchmark suite rather than a Rails benchmark
suite.
I don’t know about writing records to the DB, but for reading the AR
code is just inefficient as it involves just too many hash accesses. In
pre-1.0 times, I’ve written a patch that replaced hash operations as
much as possible with array operations[1]. The performance improvement
was noticeable, see the ticket for details. But all that was ages ago
and I haven’t updated the patch for the considerable changes that came
with Rails 1.0.
Michael
[1] http://dev.rubyonrails.org/ticket/2172
–
Michael S.
mailto:[email protected]
http://www.schuerig.de/michael/