Disabling Dehydration

In a project using Tastypie as the API component, was recently looking at performance optimisations for cases where the API has to serve relatively large datasets ~= 10K rows/objects.

Turns out that disabling the loop through the dehydrate cycle for each object gave a factor 8 speedup (worth having).

Adding an option to the resource meta to allow the user disable dehydration if they so wish would seem to be a plausible "sensible-defaults, disable for edge cases" workaround?