In Valid Logic

Endlessly expanding technology

Tracing Cache Money transactions through New Relic

At Involver, we’ve been starting to make heavy use of New Relic to start monitoring performance and track down bottlenecks. I’ve been working to add method tracers around components that utilize external APIs or services, and some of the major components we leverage to know how much time is spent in various areas.

We use Cache Money, a gem that helps transparently cache models in Memcached. Out of the box, New Relic supports tracing calls for Memcached, however on traces we’d see a long list of Memcached calls but no information as to which request they were associated with.

For a lot of our additional traces, we’ve added an rpm_extras.rb file. To include tracing for Cache Money, just need to define it as follows:

1 ::ActiveRecord::Base.class_eval do
2   class << self
3     add_method_tracer :transaction, 'Custom/CacheMoney/transaction'
4     add_method_tracer :find_every, 'Custom/CacheMoney/find_every'
5     add_method_tracer :find_from_ids, 'Custom/CacheMoney/find_from_ids'
6   end
7 end

New Relic itself uses add_method_tracer around transaction and find_by_sql, however Cache Money works by alias_method_chaining transaction, find_every, and find_from_ids.

One thing worth noting is that since both New Relic and Cache Money make use of transaction, order of loading could be important. In our environment.rb, we load our rpm_extras.rb in the after_initialize block. When RPM is loaded, it wraps the actual ActiveRecord#transaction call, then Cache Money chains it, and our own tracer wraps the chained call.

Initially, I tried putting the tracer around Cache Money’s own transaction_with_cache_transaction, however that didn’t show up in traces.

Tuesday, June 15, 2010

 
blog comments powered by Disqus