clockworklabs / clockworklabs/SpacetimeDB
Benchmarks differences in keynote-2
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
I just was taking a look and found some things im curious about, would you mind explaining why some of these differences were done (different clients and protocols mainly, as well as a lack of warmup on other clients).
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 reviewing the keynote-2 benchmark setup and the linked Hacker News discussion. Compare the client and protocol choices and the warmup behavior mentioned in the issue. Done means the benchmark differences have a documented explanation or the methodology has been clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, performance
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100