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

Experimental new bucket-style queues for feeds. #911

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Half-Shot
Copy link
Contributor

This is more of a thought-experiment-as-code more than something I think works, but anyway. Off the back of #910, I was trying to think of why you'd want to set different refresh periods. It feels like Hookshot should have enough information to figure out an "optimal" refresh period, which in turn would reduce the need for user involvement.

The ultimate goal being that feeds that are active refresh more often than ones that are not, making hookshot feel faster. Some thoughts remain thought:

  • If you end up in the very slow bucket, you may have to wait a really long time for Hookshot to get to you, which might cause it to feel broken.
  • In practice at the small scale, feeds kept flipping between the middle two buckets.
  • A lot of these values are hardcoded and should be configurable, it's also worth thinking about whether the linear scale is a sensible idea, or whether this should be logarithmic.

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

Successfully merging this pull request may close these issues.

None yet

1 participant