npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

slow-code-detector

v1.0.3

Published

Tool to show slow calls in your code runned by v8.

Downloads

6

Readme

Slow-Code-Detector

Tool to show slow calls in your code runned by v8.

Install

npm i -g slow-code-detector

How to use

scd your-index-js-file.js – it creates bunch of files in current directory code.asm hydrogen.cfg out.txt code.html

code.html – is what you need, open it in the browser.

Also you can generate markdown file code.md, just run with --md option: scd --md index.js

Generated code.html groupped by files and functions.

code.html

Every runtime call highlighted by gray. Call cost ~4ns.

Pink highlight is LoadGeneric or StoreGeneric. Generic read or write cost ~9ns.

If function in code is inlined it highlighted by blue, you can show its code by click.

If function is not inlined you can show non inline reason by a hint on call function name.

If function deoptimized, it colored by red.

Every function reoptimization marked by ~recompile~ – max 10 times, else deopt: Optimize too many times

How it works

The scd execute node with some v8 trace options and parse given logs to find slow path calls.

node --trace-inlining --trace-hydrogen --trace-phase=Z --trace-deopt

IRHydra

You can use hydrogen.cfg and code.asm with IRHydra to investigate internal representation of your code