Avoid unnecessary memory allocation and copying in wasm transport layer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- cpp, wasm
- Domain
- performance
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.
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.
- Dominant language
- C++
- Stars
- 6
- Forks
- 5
- Avg merge
- 4h 22m
- Merged PRs (30d)
- 4
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.
More from QuantStack/git2cpp
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
QuantStack/git2cpp#131 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
QuantStack/git2cpp#62 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
QuantStack/git2cpp#51 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
QuantStack/git2cpp#50 ·
All issues in QuantStack/git2cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google/libultrahdr#485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
godotengine/godot#123776 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 60/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/common_interfaces#344 ·