petkaantonov/nodeperf is tracked by TopGit as an open-source project, with 96 stars on GitHub, written primarily in JavaScript. Like a profiler but actually useful in improving performance
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
(People who see this, nodex64 are debug binaries for node which you need to build yourself. Debug build is required. I will add more elaborate instructions later).
Example:
$ nodex64 ./src/run.js test.js
In total 50 (10 unique) optimizations were done taking 0.80 seconds of compiler time.
Found 11 issues.
Critical (3):
- Function `doPhase` was hard deoptimized 11 times:
1. At bailout position 2 an assumption failed: Expected a value not to be an integer. (check-non-smi)
2. At bailout position 4 an assumption failed: Expected a value to be an integer. (check-smi)
3. At bailout position 2 an assumption failed: Expected a value to be an integer. (check-smi)
- Function `disabled` cannot be optimized because it contains a switch-statement that has case clauses that are either not integer literals or string literals
- Function `doPhase` cannot be optimized because it has been reoptimized too many times.
High (6):
- Function `THISISTHEFUNCTION` was hard deoptimized 4 times:
1. At bailout position 14 an assumption failed: Expected a value not to be an integer. (check-non-smi)
2. At bailout position 10 an assumption failed: Expected integer division operation not to be passed a 0 dividend, negative zero, not to overflow signed int32 range or have a non-zero remainder. (div-i)
3. At bailout position 8 an assumption failed: Expected an object to have a certain hidden class. (check-maps)
4. At bailout position 1 an assumption failed: Expected numeric property access not to be made out of bounds. (bounds-check)
- The small function `noInline2` when called from the function `MissingInlineOpportunities` cannot be inlined because the former creates closures.
- The small function `ClosureClass` when called from the function `redefinitionAbuse` cannot be inlined because the former creates closures.
- The small function `redefinitionAbuse` when called from the function `[anonymous]` cannot be inlined because they do not share the same scope.
- The function `ClosureClass.setAge` was re-defined at least 152 times.
- The function `ClosureClass.getAge` was re-defined at least 152 times.
Medium (2):
- The function `[anonymous]` when called from the function `MissingInlineOpportunities` cannot be inlined because they do not share the same scope.
- The function `[anonymous]` when called from the function `[anonymous]` cannot be inlined because they do not share the same scope.
Low (0):
How active is development on petkaantonov/nodeperf?
The most recent commit recorded on petkaantonov/nodeperf was 12.7 years ago, based on the GitHub push timestamp. The repository has 1 forks — one of the better signals of community interest.
How many stars does petkaantonov/nodeperf have?
petkaantonov/nodeperf has 96 GitHub stars — refresh the page for the live number, or check github.com/petkaantonov/nodeperf. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is petkaantonov/nodeperf open source?
Yes — petkaantonov/nodeperf ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/petkaantonov/nodeperf.
What is petkaantonov/nodeperf?
petkaantonov/nodeperf (petkaantonov/nodeperf) is a JavaScript project on GitHub. From the project's own README: Like a profiler but actually useful in improving performance
Where do I read more about petkaantonov/nodeperf?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/petkaantonov/nodeperf is the definitive source.
Read full README in the tab above.
Still deciding about nodeperf?
One click hands the question to an AI along with this page — see what it says about nodeperf.
