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

benchd

v0.0.2

Published

Benchmark JavaScript code across different node.js/io.js versions from the browser

Downloads

3

Readme

Description

benchd is a tool for benchmarking JavaScript code across different node.js/io.js versions from the browser.

Requirements

  • Backend: node.js -- v0.10.0 or newer

  • Frontend: Any modern browser with WebSocket support

Install

npm install -g benchd

Config

Configuration is achieved by a JSON formatted config file. If the BENCHD_CONF environment variable is set and points to a valid file, that will be used. Otherwise the server will look in the current working directory for benchd.conf. If that also fails, then defaults will be used. Any command-line arguments of the same names will override any other config source.

Available config options:

  • address - string - This is the address the server listens on. Default: 0.0.0.0

  • jobAbandonTimeout - integer - This is the amount of time in milliseconds to allow a job's owner to be disconnected before removing (and stopping, if currently executing) the job. Default: 30 * 1000

  • maxConcurrency - integer - This is the maximum number of target processes that are allowed to run at any given time. Set to -1 as an alias for the number of available CPUs. Default: 1

  • maxJobSize - integer - This is the maximum size (in bytes) for a job (the JSON stringified version, including all benchmarks). Default: 512 * 1024

  • maxQueued - integer - This is the maximum number of queued jobs. Default: 1000

  • port - integer - This is the port the server listens on. Default: 80

  • targetsPath - string - This is the directory containing the target executables to make available for benchmarking against. Default: (current working directory)

  • timeout - integer - This is the target process timeout in milliseconds. Default: 5 * 60 * 1000

  • vanilla - boolean - Restrict benchmark code to a "pure"/vanilla JavaScript environment (e.g. no require(), process, etc.). If you disable this and are making the server public, PLEASE start the server in an appropriately protected environment. Default: true

Todo

  • Add support for async ("deferred") option for benchmarks

  • Better WebSocket error handling

  • Add per-benchmark timeout configuration option

  • Ability to easily share benchmark results (can load from/save to gist right now, but no easy way to discover benchmarks)

  • Add support for remote targets (e.g. via ssh) for multi-platform benchmarking

  • Tests