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

brisky-performance

v1.4.2

Published

performance test suite

Downloads

35

Readme

#brisky-performance Simple performance benchmarking tools (browser and node)

Build Status js-standard-style npm version Coverage Status


Precise time measurement

uses hrTime, webkit.performance or Date.now

const { time } = require('brisky-performance')
const start = time() // array in node, ms in browser
const elapsed = time(start)

When called without arguments, returns a time object When called with an argument, returns the difference between the current time and the time passed in as argument, in milliseconds


Comparing functions

Compare a function vs another, usefull for writing perf tests

const perf = require('brisky-performance')
// The following test will pass if `subject` executes at least 2 times as fast as `reference`
perf(function subject () {}, function reference () {}, 2)

perf(() => {}, () => {}, 'some test')
perf (subject, reference, *margin, *loop, *label)
  • subject - function to measure
  • reference - function to compare with subject
  • margin - number of times faster subject must be compared to reference for the test to pass
  • loop - Number of times to run the functions (default: 10)
  • label - Override label

When passing a string to margin or loop it will become the label


Finding IC inconsistencies

Helps finding type mismatches in functions, just counts them. Usefull when you see the v8 warning "optmized too many times" It's usualy too many type differences passed into the arguments

const { type } = require('brisky-performance')
function someFunction (a, b) {
  type.test(someFunction, a, b)
}
someFunction('hello', 1)
someFunction([ 1, 2 ], null)
type.someFunction //  →
// {
//   a: { string: 1, array: 1 },
//   b: { number: 1, null: 1 }
// }

type.test('customkey', someFunction, 1, 2)
type.customkey // → { a: { number: 1 }, b: { number: 1 } }

Uses tape internally, which produces TAP (Test Anything Protocol) output.