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

profiler

v1.2.3

Published

Access the V8 profiler from node.js

Downloads

35

Readme

node-profiler

Access the V8 profiler from node.js - http://nodejs.org/

Deprecation notice

This module is effectively deprecated. Newer versions of V8 have removed much of the functionality that node-profiler depends on. As a result, it's become much less effective.

Consider using strong-agent if you want on-demand CPU profiling.

A word of advice

This module is for people who need fine-grained run-time control over the V8 profiler. You don't need it if all you want is wholesale profiling, simply start node with profiling enabled:

node --prof application.js

Read on, however, if you want to wield the arcane powers this module grants.

Compiling

Easy as pie. To build from source:

node-gyp configure build install

Or, if you have npm installed:

npm install profiler

Usage

In most cases you will want to start your application with the profiler in suspended animation.

node --prof --prof_lazy --log application.js

And inside your application:

var profiler = require('profiler');
//
// <here be code you don't want to profile>
//
profiler.resume();
//
// <performance critical code here>
//
profiler.pause();

This results in a v8.log being written to the current directory that you can process with the bundled nprof tool. Run sh tools/build-nprof to build it.

Advanced usage

You will sometimes want to run the garbage collector before profiling a performance critical section of code. Here is how you do it:

$ cat application.js
if (typeof gc === 'function') gc();
profiler.resume();
// ...
$ node --prof --prof_lazy --log --expose-gc application.js