microsoft / microsoft/TypeScript
Investigate batching/streaming of AST transfer
Open
Nobody has claimed this yet.
Domain: API
Domain: Performance
In Discussion
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
In migrating towards the TS7 APIs for building VS Code, @dbaeumer found a potential bottleneck in AST encoding/decoding - a significant amount of time is actually taken up on the server side.
We should look into the following:
- Batching AST requests (client side)
- Asynchrononous responses for AST encoding (async client side)
- Possibly streaming responses? (async(?) client side)
- Parallel AST encoding (server side)
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
No files or tests are named. Start by tracing the TS7 API AST encoding and decoding path on both client and server, then measure the current transfer costs. Done means evaluating batching, asynchronous responses, streaming, and parallel server-side encoding well enough to identify an implementation direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, compilers, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100