Emi Matchu 583f3c712f High-level caching for closet lists ... Okay, so I still don't know why rendering is just so slow (though migrating away from item translations did help!), but I can at least cache entire closet lists as a basic measure. That way, the first user to see the latest version of a closet list will still need just as much time to load it… but *only* the ones that have changed since last time (rather than always the full page), and then subsequent users get to reuse it too! Should help a lot for high-traffic lists, which incidentally are likely to be the big ones belonging to highly active traders! One big change we needed to make was to extract the `user-owns` and `user-wants` classes (which we use for trade matches for *the user viewing the list right now*) out of the cached HTML, and apply them after with Javascript instead. I always dislike moving stuff to JS, but the wins here seem. truly very very good, all things considered!		2024-02-20 18:43:39 -08:00
..
_item.html.haml	Move item_link partial caching to a helper rather than the template itself	2013-06-22 16:31:46 -07:00
_item_header.haml	Add "first seen" timestamps to item pages	2024-02-20 14:32:45 -08:00
_item_link.html.haml	High-level caching for closet lists	2024-02-20 18:43:39 -08:00
index.html.haml	Remove newest_items caching from items page	2023-10-23 19:05:04 -07:00
needed.html.haml	Update most URLs to use HTTPS	2023-10-25 15:22:57 -07:00
show.html.haml	Oops, load the data for the bulk item quantity form on the trades page!	2024-01-21 06:42:24 -08:00