Exclude inga and add FDB-backed indexers as provider backends
#2011
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`inga` is suffering from high CPU usage, despite reduction of worker count by 10X and increase of CPU resource by ~3X. This level of CPU consumption seems unreasonable and causes latency fluctuation in lookups. Further, it causes high rate of 404s due to provider lookups via dhfind instances failing. Therefore it is now excluded as a provider backend. Include new FDB backed instances as provider backed since they now have 100% coverage of providers.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ingais suffering from high CPU usage, despite reduction of worker count by 10X and increase of CPU resource by ~3X.This level of CPU consumption seems unreasonable and causes latency
fluctuation in lookups. Further, it causes high rate of 404s due to provider lookups via dhfind instances failing. Therefore it is now excluded as a provider backend.
Include new FDB backed instances as provider backed since they now have 100% coverage of providers.