QuantStack / QuantStack/git2cpp
Avoid unnecessary memory allocation and copying in wasm transport layer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6
- Forks
- 5
- Avg merge
- 4h 22m
- Merged PRs (30d)
- 4
Description
There are opportunities to improve the performance of the wasm transport layer. It necessarily includes marshalling of data between JavaScript and C++, but I think some of this can be improved as there are some unnecessary allocations of temporary buffers where we can probably just reuse the same buffer, and we may well be doing more copies of data than are strictly necessary.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the wasm transport layer and tracing how data is marshalled between JavaScript and C++. Measure temporary buffer allocations and data copies first; done means unnecessary allocations or copies are reduced without changing transport behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, wasm
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100