Make scores information faster for large installs

[Krinkle]

It takes minutes to load for jquery

[hashar]

/scores/ could be either paginated or limited to the top 50 users.

[Krinkle]

As of 1.0.0-pre we have a primitive caching system. But just caching it doesn't help very well in this case because it still takes well over a minute to generate on large swarms, and every now and then the cache has to expire and be regenerated. We should somehow defer the calculation of it in smaller chunks and cache those.

Or, alternatively, in the spirit of "optimizing TestSwarm for automated testing" and improving the individual user/project view, and removing support for giant views for all projects and all users of all time.... we could also remove the Scores action/page and instead just show a score on the UserPage of each user.

Those queries are a lot faster to calculate (might still lag eventually, but should be manageable), and users can still see their score and compare themselves to (known) friends by looking another UserPage.

We might even cache it from there and then bring back the ScoresPage to show the cached scores of each user.

[jzaefferer]

At least for swarm.jquery.org this isn't an issue anymore. The Scores page might as well be removed, as only authenticated clients (via runToken) are accepted. Are Wikimedia TestSwarm clients still interested in their scores?

[Krinkle]

Well, regardless of interest I slammed this bug on its head with 4be762e.

No need for cache implementation (yet). Looks like even our swram.jquery.org is performing in well under a second for the scores page (it used to timeout after 30 seconds).