1
0
Fork 0
forked from OpenNeo/impress
impress/app/views/closet_lists
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
..
_closet_list.html.haml High-level caching for closet lists 2024-02-20 18:43:39 -08:00
_form.html.haml refactor closet_lists.form hierarchy 2013-01-09 17:38:03 -06:00
_trading_neomail_warning.html.haml warn users with trading lists but no neomail address 2014-12-02 10:05:11 -06:00
edit.html.haml i18n for closet_hangers#index, closet_lists#edit, closet_lists#new, and maybe some more closet-related things - this was a biggie 2013-01-09 17:15:24 -06:00
new.html.haml i18n for closet_hangers#index, closet_lists#edit, closet_lists#new, and maybe some more closet-related things - this was a biggie 2013-01-09 17:15:24 -06:00