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

another-v8-profiler

v3.7.2

Published

node bindings for the v8 profiler, minus the retain/dominator bits removed from V8

Downloads

7

Readme

v8-profiler provides node bindings for the v8 profiler and integration with node-inspector

Installation

npm install another-v8-profiler

We now include node v0.10 binaries for a number of platforms. During the install, node-gyp will attempt to build the module for your platform. If it fails (see builderror.log), the module will still be installed, but will attempt to load up an appropriate pre-built binary for your platform if there is one available.

Usage

var profiler = require('another-v8-profiler');

API

######profiler properties

heapProfiler
cpuProfiler

######cpuProfiler properties

count = getProfilesCount()
cpuProfile = getProfile(index)
cpuProfile = findProfile(index)
startProfiling([name])
cpuProfile = stopProfiling([name])
deleteAllProfiles()

######cpuProfile properties

string = getTitle()
integer = getUid()
string = getType()
Serialize( opts={onData: fn, onEnd: fn} )
Delete()
boolean = save([filename])

######heapProfiler properties

count = getSnapshotsCount()
heapSnapshot = getSnapshot(index)
heapSnapshot = findSnapshot(index)
heapSnapshot = takeSnapshot([name])
deleteAllSnapshots()

######heapSnapshot properties

string = getTitle()
integer = getUid()
string = getType()
Serialize( opts={onData: fn, onEnd: fn} )
Delete()
boolean = save([filename])

Examples

var profiler = require('another-v8-profiler');
var heapProfiler = profiler.heapProfiler;
var snapshot = heapProfiler.takeSnapshot([name])    // takes a heap snapshot
snapshot.save(filename);                            // save the snapshot to file
snapshot.delete();                                  // delete the snapshot (releases memory)
var profiler = require('another-v8-profiler');
var cpuProfiler = profiler.cpuProfiler;
cpuProfiler.startProfiling([name])                  // begin cpu profiling
var cpuProfile = profiler.stopProfiling([name])     // finish cpu profiling

node-inspector

Cpu profiles can be viewed and heap snapshots may be taken and viewed from the profiles panel.