I had a long conversation with Tim & Coleman on IRC about the approach to this & to caching report results (the 2 intersect). The upshot is that we can probably solve this without solving that & there is still a bit to ponder about the latter. I'm going to distill the discussion (attached) into 2 JIRA tickets.

Spoiler alert - frobnicating is not as bad as it sounds.

OK - I've translated that conversation into 2 separate JIRA for when we are ready to prioritise them

Render dashlets
https://issues.civicrm.org/jira/browse/CRM-17663

Cache report results
https://issues.civicrm.org/jira/browse/CRM-17664

There might be an Nginx way to do this.

I've pulled this into the sprint because someone has submitted a patch to civicrm core that should fix this https://github.com/civicrm/civicrm-core/pull/7666

I'll test the patch & give feedback as to whether it should be merged to core (and if it works deploy it for us too)

I just tested & reviewed the PR here https://github.com/civicrm/civicrm-core/pull/7666

Unfortunately it didn't work for me yet - I've given her feedback on it - so we don't have the quick win here I was hoping for.

This can potentially be de-prioritised in the hope the submitter does some more work on this in the meantime

Hey @Eileenmcnaughton did the submitter make any headway?

I haven't seen any more on it

@awight Do we want to move forward with this project?

From Coleman (coleman@civicrm.org)
This seems like a good project for the core team and a nice win for CiviCRM. Let me know if you'd like to proceed.
I think this would be roughly a 15 hour job. Rates are $125/hr for members, $175/hr for non-members. (Rough range: $1800 - $2600)
If you guys are thinking of signing up for membership, now would be a good time :)
https://civicrm.org/membership