Thanks, all, for the great suggestions. This issue was driving me a little crazy because the performance was so atrocious. I started down the road of moving the update to a background process but thought I should dig a little deeper to understand why it was so glacial in the first place.
It turns out that while I thought I was iterating over a list of attributes that should have been no more than 6 I was in fact iterating over the attributes of a model instance (67 in this case). Do that 300 or so times and things are a bit slower than they should be! Two take-aways from this: - Don't optimize prematurely. - Before you optimize, make sure you fully understand what's driving you to optimize. Maybe you don't need to! Cheers, Chris -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
