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

Slow response on scatter gather requests #86

Closed
masih opened this issue Feb 23, 2023 · 1 comment
Closed

Slow response on scatter gather requests #86

masih opened this issue Feb 23, 2023 · 1 comment
Assignees
Labels

Comments

@masih
Copy link
Member

masih commented Feb 23, 2023

After introducing logic to fall back on streaming content type it seems responses are generally slower. See latency observed by hydra boosters for example:

image

@masih masih self-assigned this Feb 23, 2023
@masih masih added the P0 label Feb 23, 2023
masih added a commit that referenced this issue Feb 23, 2023
Refactor backend instantiation such that circuit breaker backends are
individually configurable. Reflect changes across the repo.

Add the ability to check if a backend matches a request before
attempting to call it. This avoids response slow-down caused by slow
backends early in the chain

Introduce a separate configuration to mark cascade lookup backends with
explicit matcher in order to avoid routing all requests to them.

Relates to:
 - #86
masih added a commit that referenced this issue Feb 23, 2023
Refactor backend instantiation such that circuit breaker backends are
individually configurable. Reflect changes across the repo.

Add the ability to check if a backend matches a request before
attempting to call it. This avoids response slow-down caused by slow
backends early in the chain

Introduce a separate configuration to mark cascade lookup backends with
explicit matcher in order to avoid routing all requests to them.

Relates to:
 - #86
masih added a commit that referenced this issue Feb 23, 2023
Refactor backend instantiation such that circuit breaker backends are
individually configurable. Reflect changes across the repo.

Add the ability to check if a backend matches a request before
attempting to call it. This avoids response slow-down caused by slow
backends early in the chain

Introduce a separate configuration to mark cascade lookup backends with
explicit matcher in order to avoid routing all requests to them.

Relates to:
 - #86
@masih
Copy link
Member Author

masih commented Feb 23, 2023

Fix deployed at 1700 UTC on prod. latency fluctuations settled now:
image

nft.storage coverage is growing steadily with no fluctuations:
image

caboose fetch errors are more or less flat since:
image

Marking as fixed.

@masih masih closed this as completed Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant