I've had the exact same experience. Rabl is horribly slow in template generation... Also, FWIW-- older versions of AMS, with caching, are a total crapshoot due

I've had the exact same experience. Rabl is horribly slow in template generation... Also, FWIW-- older versions of AMS, with caching, are a total crapshoot due to marshal dumping the objects into the cache and re-serializing them to JSON each time. Much better to cache the response itself instead of the objects making up the response. Granted the caching feature was yanked out of AMS, but pretty painful for those of us that actually tried using it. Carrierwave + AMS caching = Problemzilla At this point, we too have had Rabl, AMS, and Representers and the best one of the lot-- by far, for our use cases has been: Roar. https://github.com/apotonick/roar-rails https://github.com/apotonick/roar-rails Plus, it's the only system which will de-serialize the data using the representer. Boom-shaka-laka.