clockworklabs / clockworklabs/SpacetimeDB
Cache compiled native code produced from wasm modules
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
The main reason I'm interested in this is that it could speed up benchmarks run under callgrind by a lot. Note that it's possible to compile wasm modules while running callgrind, just quite slow.
This should probably wait until after we validate + merge wasmtime (since callgrind doesn't play nice with wasmer, but likes wasmtime.)
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
No files or tests are named. First validate and merge wasmtime, then investigate the wasm compilation path and how callgrind behaves with wasmer versus wasmtime. Done means compiled native code from wasm modules is cached and callgrind benchmarks avoid repeated slow compilation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100