Performance improvements for upload_graph
Open
Nobody has claimed this yet.
GraphQL
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
have a look at the implementation of upload_graph and try to skip as much steps as possible from the validation process. For instance, avoid having to re-encode the graph again.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the implementation of upload_graph and trace its validation process, focusing first on where the graph is re-encoded. Identify which validation steps can be skipped without changing the operation's behavior; done means upload_graph avoids redundant work while preserving validation correctness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100