sdsykes / slim-attributes

Boosts speed in ActiveRecord models with mysql by lazily instantiating attributes as needed.

This URL has Read+Write access

sdsykes (author)
Mon Apr 06 12:59:40 -0700 2009
commit  c313d72e96a6d30ae884a4ce34d3e398765f92f9
tree    cb41052bbd03729602f09ef4346bada137f94ca2
parent  fa9390807462a96fa1c7cb73b4c1a3a2db915fef
README
SlimAttributes
==============

This is a small patch to the ActiveRecord Mysql adaptor that stops rails from using the all_hashes / each_hash mechanism 
- which is what is called when you do a find.

It is faster, and uses less memory.

Measuring with just ActiveRecord code - fetching stuff from the database - we see anything up to a 50% (or more) speed 
increase, but I suppose it really depends on your system and environment, and what you are doing with the results from 
the database.  The more columns your tables have, the better the improvement will likely be.  Measure your own system 
and send me the results!


Installation
============

You're going to need the mysql headers for this to work.

Try:
gem install slim-attributes -- --with-mysql-config
or:
gem install slim-attributes

then add this to environment.rb:
require 'slim_attributes'


Description
===========

The reason for overriding all_hashes is threefold:

* making a hash of each and every row returned from the database is slow
* ruby makes frozen copies of each column name string (for the keys) which results in a great many strings which are not 
really needed
* we observe that it's not often that all the fields of rows fetched from the database are actually used

So this is an alternative implementation of all_hashes that returns a 'fake hash' which contains a hash of the column 
names (the same hash of names is used for every row), and also contains the row data in an area memcpy'd directly from 
the mysql API.

The field contents are then instantiated into Ruby strings on demand - ruby strings are only made if you need them.  
Note that if you always look at all the columns when you fetch data from the database then this won't necessarily be 
faster that the unpatched mysql adapter.  But it won't be much slower either, and we do expect that most times not all 
the columns from a result set are accessed.


===========

No warranty - this gem has been tested, but not in all environments.  However, that said, we are using it in our 
production environment with good results.
Please report bugs to sdsykes at symbol gmail pip com.

Copyright (c) 2008 Stephen Sykes, released under the MIT license