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

simple_async_perf_tester

v2.0.6

Published

Simple, independent async code performance tester

Downloads

2

Readme

Simple, independent async code performance tester 🕵️

Install

npm i --save-dev simple_async_perf_tester or yarn --dev simple_async_perf_tester

Usage

const perfTest = require("simple_async_perf_tester"); // or ES6 import

perfTest({
  numberOfRuns: 5,
  scriptName: "script.js",
});
perfTest({ scriptName: "anotherScript.js" });

// Example output:
/**
 * Running Performance Testing 🕵️‍♂️
 * - Number of runs: 200
 * - Test script: example.js
 *
 * RESULT:
 * - Average parsing time is 5.98ms
 */

Options

Options to pass to the performace execution function

const options = {
  numberOfRuns: 100, // OPTIONAL. A positive integer. Defaults to 50
  scriptName: "parse.js", // Path to the testing script that outputs delta execution time. See `examples` folder
}

Example test scripts

Check examples folder

Reason

I decided to save this example repo because of unexpected issues I ran into while testing async code execution using Promise.all. What I observed is that by increasing the number of runs, the average execution time increased linearly.

By moving each execution to its own process, the test is unbiased and independent of current process resources being taken by past executions. Unfortunately, the approach here makes the execution of the performance test longer.