Skip to content

tackle startup cost issue #174

Open
Open

Description

@tomellm

On startup our application needs to do a number of requests to fill up the caches. This incurrs a large number of requests and makes the ratelimiter stop all requesting.

To avoid this situation our idea was to only have the ApiRateLimitStatus raise by one each time and not jump from best to worst.

Activity

  1. self-assigned this
    on May 30, 2024
  2. added 5 commits that reference this issue on May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions