Can you give me some idea what URLs we're talking about for "education dashboard pages"? I'm lost.

@BBlack
Oops--these are currently hosted on labs, at http://outreachdashboard.wmflabs.org/ and https://wikiedu-dashboard-staging.wmflabs.org/

This is a Ruby on Rails app, hosted on WMF Labs for the near term. We're still a few months away from an alpha release.

From my perspective, caching is less about the page load time, and more about reducing the potential for accidental DOS caused by logged-out users and crawlers hitting expensive Ruby pages.

We don't cache labs services in production, and we don't currently (AFAIK) have any kind of cache_misc equivalent in the beta cluster either. Basically, when the service itself is ready for production use in terms of code/deployment and moves into production hosting, we can then put it behind our standard caches and TLS termination. We can initially put it there as a pass-only service (no caching) if we're unsure how these services interact with caching, and we can start caching it if/when you think it's ready (in terms of RFC-standard cacheability headers and cookie handling, etc...).

Wonderful, thanks for the helpful overview! I'm sure it will be fine to do an initial deployment without caching, and we'll get a good idea of how much load the app server is under.

@awight: is there anything to do here or can we close the task?