Here are a few thoughts I had a year or so backy for some potential
low hanging fruit for speeding rails up [if anybody ever wants to
implement them :)

Forgive the naivety of these, they're mostly just suggestions from
someone not all that familiar with the core code.

1) wrap tests in transactions.  Since rails now has nested
transactions, it may be possible to speedup unit tests, via something
like http://ericholscher.com/blog/2009/jan/15/django-now-has-fast-tests/

2) don't write the session out if it hasn't changed at all during a
request.

3) don't regenerate query plans every time [cache them if possible].

4) avoid n^2 filter searches as you handle a request [I believe that's
what it does currently].  At least with the before and after filters,
you could calculate them all once, at the beginning of the request.

5) Avoid re-generating sql escaped copies of each column name for
tables.  Cache the sql escaped column names.

6) LRU cache all sql-escaped data [?]

8) use array based queries instead of hash based.  Oh wait you already
knew that one.

Anyway thanks for reading.
Have a good one.
-=r
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to