Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publicize requested:granted ratio #22

Open
hannahwhy opened this issue Aug 29, 2014 · 1 comment
Open

Publicize requested:granted ratio #22

hannahwhy opened this issue Aug 29, 2014 · 1 comment

Comments

@hannahwhy
Copy link
Member

The swipnet project is servicing ~13000 requests/minute for items, but the target servers can only really handle ~500 concurrent items. As a result, most of those 13000 requests are walking away empty.

Furthermore, the "Tracker rate limiting is active" message does not seem to communicate what we thought it'd communicate. People tend to see it as an error rather than a "slow down" notice.

I think making some more global information available might help:

[10:04:29] <yipdw> or maybe just making the requested:granted ratio public
[10:05:02] <yipdw> will help illustrate that the right thing to do in a rate-limiting situation is not to drive the request rate higher
[10:05:07] <arkiver> maybe in the upper right corner
[10:06:01] <yipdw> it's possible that one motivation to start up a billion pipelines is lack of global information
[10:06:16] <yipdw> if we provide that maybe it'll help illustrate what "3300% of demand" means

We could also return this information as part of the "rate limited" response, which would make it possible to display that information in the "tracker rate limiting is active" message.

@chfoo
Copy link
Member

chfoo commented Sep 12, 2014

Cross reference: ArchiveTeam/seesaw-kit/issues/7

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

No branches or pull requests

2 participants