Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

Trending teams #3939

Closed
mattbk opened this issue Mar 4, 2016 · 11 comments
Closed

Trending teams #3939

mattbk opened this issue Mar 4, 2016 · 11 comments

Comments

@mattbk
Copy link
Contributor

mattbk commented Mar 4, 2016

Could calculate and display teams that are showing the most growth in either number of givers or amount being received. Stats page or part of a more general "find teams" system (#3127, #3938, etc.).

@aandis
Copy link
Contributor

aandis commented Mar 4, 2016

#3736?

@mattbk
Copy link
Contributor Author

mattbk commented Mar 4, 2016

I think that's related, but in order to incorporate #3127 it might need to not be on the front page. Or maybe that's a simple dropdown in the UI that could be made to look okay.

ETA: Or are you saying that "trending" could be one of the sorts for #3736? I think that could work like that idea.

@aandis
Copy link
Contributor

aandis commented Mar 4, 2016

number of givers or amount being received.

I meant these two could be part of those sort, but the sorting thing will probably be on the homepage.

@mattbk
Copy link
Contributor Author

mattbk commented Mar 4, 2016

How often would the "trending" calculator run? I assume we have other processes that run on a schedule, could this be rolled in to recalculate a database value for is_trending?

@chadwhitacre
Copy link
Contributor

FYI we do have some cron-ish infrastructure.

@chadwhitacre
Copy link
Contributor

We might also consider migrating cron-ish work out of the web app and over to @gratipay-bot.

@mattbk
Copy link
Contributor Author

mattbk commented Mar 4, 2016

We might also consider migrating cron-ish work out of the web app and over to @gratipay-bot.

Out of curiosity, why?

@chadwhitacre
Copy link
Contributor

Because it's hackish to have async tasks running in a thread in the main web app server. It makes it complicated to scale beyond one webserver, because one generally wants to scale async workers separately from web workers.

@mattbk
Copy link
Contributor Author

mattbk commented Mar 4, 2016

It makes it complicated to scale beyond one webserver, because one generally wants to scale async workers separately from web workers.

Ahh, that makes sense. So @gratipay-bot could do its thing over multiple servers if needed, whereas crontab would need to be mirrored to each machine.

@mattbk
Copy link
Contributor Author

mattbk commented Mar 14, 2016

Inspiration at http://github.com/explore:

image

Twitter:
image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants