fix: use direct HTTP forwarding to improve /status endpoint performance #886
+302
−44
Conversation
This file contains hidden or 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
Replace complex GraphQL abstraction layers with direct HTTP forwarding to graph-node. This eliminates redundant parsing and serialization that caused ~15s response times vs ~0.4s for direct graph-node queries. Changes: - Remove async_graphql_axum::GraphQLRequest extractor - Remove WrappedGraphQLRequest conversion wrapper - Remove thegraph_graphql_http::send_graphql abstraction - Use raw Bytes and direct .body().send() pattern - Add debug timing instrumentation for troubleshooting Fixes #540
suchapalaver
force-pushed
the
540-status-endpoint-slow-responding
branch
from
f500bf3 to
d0fe0c1
Compare
Pull Request Test Coverage Report for Build 19945495174Details
💛 - Coveralls |
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.
Replace complex GraphQL abstraction layers with direct HTTP forwarding to graph-node. This eliminates redundant parsing and serialization that caused ~15s response times vs ~0.4s for direct graph-node queries.
Changes:
Fixes #540
Signed off by Joseph Livesey joseph@semiotic.ai