Skip to content
This repository has been archived by the owner on May 2, 2020. It is now read-only.

Resource managemernt #12

Closed
SQL-enwiki opened this issue May 5, 2019 · 3 comments
Closed

Resource managemernt #12

SQL-enwiki opened this issue May 5, 2019 · 3 comments
Labels
wontfix This will not be worked on

Comments

@SQL-enwiki
Copy link
Owner

Implement a resource management system using the groundwork laid in stats.php

As a user uses 5% of our current lowest provider's allowed queries, start throttling / delaying requests more aggressively until they reach 10%, at which point no further queries will be allowed until the beginning of the next calendar month.

Possible alternate would be adding hourly/daily/monthly hard limits per user. This may be preferable to intentionally degrading the service, as well as being easier to implement.

@SQL-enwiki
Copy link
Owner Author

Not needed due to a successful grant request.

@SQL-enwiki
Copy link
Owner Author

It may be worth revisiting this. We've run out of ipstack montly queries, and getipintel daily queries. GetIPIntel has graciously donated us a higher limit key.

@SQL-enwiki SQL-enwiki reopened this Jan 28, 2020
@SQL-enwiki
Copy link
Owner Author

Possibly a 500 query per user limit? That seems pretty reasonable at the moment, most of the heaviest users only get to just under 1/2 of that.

@SQL-enwiki SQL-enwiki added the wontfix This will not be worked on label May 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant