-
-
Notifications
You must be signed in to change notification settings - Fork 834
bench: update benchmarks to measure affirmative/negative test values #1428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… measure affirmative/negative test values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👋 Hi there! 👋
And thank you for opening your first pull request! We will review it shortly. 🏃 💨
Hi @soumajit23 can you please populate the PR description so that we can identify what this PR is trying to do? |
Hi @Pranavchiku! thanks for the feedback. Will do. |
is-cube-number
benchmarks to…is-cube-number
benchmarks to measure affirmative/negative test values.
@Pranavchiku please check the description. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, apply changes and this PR will be ready to merge.
lib/node_modules/@stdlib/assert/is-cube-number/benchmark/benchmark.js
Outdated
Show resolved
Hide resolved
lib/node_modules/@stdlib/assert/is-cube-number/benchmark/benchmark.js
Outdated
Show resolved
Hide resolved
is-cube-number
benchmarks to measure affirmative/negative test values.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@soumajit23 Thank you for working on this. A couple of comments:
- When adding benchmarks measuring perf for true and false cases, the values need to actually evaluate as those values. E.g., for the
true
case, valid values are8
,27
,64
, etc. - You removed
isObject
andisPrimitive
benchmarks. These should be restored. The expectation is that this PR should double the number of benchmarks by adding additional benchmarks for each API (the main export,isPrimitive
, andisObject
).
|
@soumajit23 Don't rebase unless you need to. In this case, you don't need to pull in the latest upstream changes for what you are working on. |
I don't think the errors are due to your code. This seems to have been caused by a recent merge which contained a bug in its example code (cc @Planeshifter and @Pranavchiku). |
@kgryte please check. |
isCubeNumberBenchmarks(NEW).txt |
@Pranavchiku @kgryte hello, |
Signed-off-by: Soumajit Chatterjee <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the benchmark values. PR should be ready to land.
Partially resolves #1148
Description
This pull request:
assert/is-cube-number
benchmarks to measure affirmative/negative test values in separate benchmark runs to have a better handle on performance depending on the input value type.Related Issues
This pull request:
@stdlib/assert/*
benchmarks to measure affirmative/negative test values #1148Questions
No.
Other
Benchmark results after refactor: isCubeNumberBenchmarks.txt
Checklist
@stdlib-js/reviewers