Matchu 816584f177 Move item_link partial caching to a helper rather than the template itself ... This is a surprisingly huge performance gain. On my testing (with cache_classes set to true to also cache templates), this sped up closet_hangers#index rendering by a factor of 2 when there were a significant number of items. Cool beans. I think we can even hold off on the individual hanger caching now: we've made the closet hanger partial tons faster by moving forms out of them and doing this cache check earlier. I'm expecting significant performance gains both here and on items#index (though less so there). I'll deploy and see how much it helps in production; if not enough, we can look at the layered caching of hangers, lists, groups, full pages, etc. So glad we don't *have* to move to a pagination model!		2013-06-22 16:31:46 -07:00
..
assets	move closet-hanger-destroy form to JS	2013-06-22 15:45:59 -07:00
controllers	import items to a specific list	2013-04-09 15:50:33 -05:00
flex	user:owns, user:wants queries	2013-01-25 10:35:35 -06:00
helpers	Move item_link partial caching to a helper rather than the template itself	2013-06-22 16:31:46 -07:00
models	move closet-hanger-destroy form to JS	2013-06-22 15:45:59 -07:00
views	Move item_link partial caching to a helper rather than the template itself	2013-06-22 16:31:46 -07:00