747151 - Improve caching for kumascript -> kuma requests

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: KumaScript, defect, P1)

Description

[Les Orchard [:lorchard]]

Caching for requests from kumascript to kuma has suddenly become much more important.

Many pages will auto-require around 10 other templates, and for a page that requires lots of templates... that's a lot of HTTP requests.

Comment 1

[Les Orchard [:lorchard]]

Looks like a partial fix for this has been done on the KumaScript side:

https://github.com/mozilla/kumascript/commit/f05d343b04005d2bb9e688ca7d72130535e380c6

There's no conditional GET, but kumascript template loaders do cache kuma source in memcache. But, there's also no cache invalidation when the kuma source changes, unless a force-refresh is done.

So, some conditional GET will help invalidation. Along with that, KumaScript could "cheat" by spying on Kuma's entries in memcache. Those can give access to the last-modified timestamps of Kuma documents once bug 753483 starts stashing those.

Comment 2

[Les Orchard [:lorchard]]

I think this is mostly improved:

https://github.com/mozilla/kumascript/commit/2d377e61d01eb8ea2af64e386bbfefe90836215e

Going to call this done, at least with respect to July launch. There is lots of caching, and it can always be improved. But, it's probably good enough for now.

Comment 3

[John Karahalis [:openjck]]

Closing as per comment 2. We can open different bugs for further improvements.