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

perf

v0.0.0

Published

nanømsg style performance benchmarks

Downloads

70

Readme

The more sand has escaped from the hourglass of our life, the clearer we should see through it.

Niccolo Machiavelli

nanømsg style performance benchmarks

conduct throughput observation and latency analysis on your endpoint to endpoint transport limits.

we use a make command with a generic configuration, just a starting point of about 100,000 small node buffers.

we examine typical udp Datagram throughput top-ends by extending this buffer envelope size to 6000 bytes.

let's collect nanomg style benchmarks for comparing various node modules!

some of the available modules among this repertoire include:

  • node-nanomsg
  • udp (node core)
  • net (node core)

setup

$ git clone https://github.com/reqshark/perf.git && cd perf && make

run

run nanomsg:

$ make perf

run the udp module:

$ make udp

run the net module:

$ make net

for more info how to bulid your own custom comparisons check out: running benchmarks

you are strongly encouraged to fork and tweak the Makefile's bench and then run:

$ make bench

:)

compatibility: node versions v0.10 up through io.js latest

Contributing

PRs for more benchmarks please! Play around with the Makefile and add directories for new modules in your PR! Don't forget to add new make commands and list them at the top .PHONY

Issues are more than welcome!

MIT