Matchu 9e3cac82ec use proxies for item html, too ... Some lame benchmarking on my box, dev, cache classes, many items: No proxies: Fresh JSON: 175, 90, 90, 93, 82, 88, 158, 150, 85, 167 = 117.8 Cached JSON: (none) Fresh HTML: 371, 327, 355, 328, 322, 346 = 341.5 Cached HTML: 173, 123, 175, 187, 171, 179 = 168 Proxies: Fresh JSON: 175, 183, 269, 219, 195, 178 = 203.17 Cached JSON: 88, 70, 89, 162, 80, 77 = 94.3 Fresh HTML: 494, 381, 350, 334, 451, 372 = 397 Cached HTML: 176, 170, 104, 101, 111, 116 = 129.7 So, overhead is significant, but the gains when cached (and that should be all the time, since we currently have 0 evictions) are definitely worth it. Worth pushing, and probably putting some future effort into reducing overhead. On production (again, lame), items#index was consistently averaging 73-74ms when super healthy, and 82ms when pets#index was being louder than usual. For reference is all. This will probably perform significantly worse at first (in JSON, anyway, since HTML is already mostly cached), so it might be worth briefly warming the cache after pushing.		2013-06-26 23:50:19 -07:00
..
assets	move closet-hanger-destroy form to JS	2013-06-22 15:45:59 -07:00
controllers	use proxies for item html, too	2013-06-26 23:50:19 -07:00
flex	Use item proxies for JSON caching	2013-06-26 23:01:12 -07:00
helpers	Move item_link partial caching to a helper rather than the template itself	2013-06-22 16:31:46 -07:00
models	use proxies for item html, too	2013-06-26 23:50:19 -07:00
views	stop caching item preview species images, and fix the bad query instead	2013-06-23 22:35:27 -07:00