mcollina / mcollina/async_bench
Rewrite it to avoid all statistical analysis
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
It is way better doing statistical analysis in a post processing phase, for example with R.
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, tests, or entry points are named. Inspect the benchmark framework to identify where statistical analysis occurs, then define the post-processing boundary; done means the framework avoids that analysis and leaves it for a tool such as R.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, r
- Domain
- performance, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100