max-mapper / max-mapper/level-row-versioning-benchmarks
make benchmark more scientific
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
you need a model about what kind of changes you are expecting. "25 versions per item" is not a realistic model. better to measure how performance changes with respect to number of versions, and then come up with a data model model (i.e. a model of how the database is actually used) likelyhood that there is an insert, update, delete, or read.
I'm doing a talk on scientific benchmarking at jsconf au next month, so I can help you with this, as I'll need to generate some material for my talk anyway.
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
The issue names no benchmark files, tests, or entry points. Start by locating how the current benchmark fixes “25 versions per item,” then define measurements across version counts and a workload model covering insert, update, delete, and read likelihoods; done means the benchmark reports performance changes under those stated workloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100