jsbench / jsbench/jsbench.github.io
show operation time / duration in nanoseconds
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 263
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
currently, only the operation frequency is displayed in operations per second = hertz
to me, getting the operation time feels more natural
like code A needs 10 nanoseconds, code B needs 100 nanoseconds
(smaller is better)
its just more intuitive than comparing
100.000 ops/sec vs 10.000 ops/sec
(larger is better)
also, when you time different components of one larger program
you can easily summarize the time-values
ideally make this optional, so we can switch between time and frequency
maybe with a per-test preset config, stored in the github-gist
Contributor guide
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. Trace where operation frequency is displayed and where per-test settings are stored in the GitHub Gist; define the duration display and optional frequency/time switch there, then verify both units and preset persistence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100