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

node-turbotest

v1.0.0

Published

A quick and easy speed tester for uWebSockets and WS.

Downloads

4

Readme

node-turbotest

A quick and easy speed tester for uWebSockets and WS.

Note: Look at the example for help. You can probably figure it out from there.

Usage

var turbotest = require('node-turbotest'); and call turbotest on connection.

wss.on('connection', function (ws) {
    turbotest.test(ws);
    // do some unrelated stuff down here...
});

Listen for any non-specific test with data.

// m is megabit per second, one-eighth of a megabyte
turbo.on('complete', function (m) {
    console.log("The clients' speed is " + m + " mbps.");
})

~~Test a specific client.~~ I guess gone, until a pull request comes or someone answers this.


Why did I build it?

I'm building a real-time engine that requires knowledge of all clients' mbps speed. Through this, Kitten will have better and more consistent streaming. And this might be grounds for machine learning, too!

Fun fact

A megabit is not a megabyte. When an ISP says, "You get 10 mbps for this plan," it does NOT mean an average sized app download (50 MB) in 5 seconds; it would be 40 seconds. A megabit is one-eighth of a megabyte. Thus, the library emits just a megabit to avoid confusion. Multiply that times 8, and you have megabyte.

Notes

This library only supports measuring download speed of the client. Trying upload resulted in NaN (Not a Number) mbps. This is all I really need, so if you need it, you can implement it, and I would be more than happy to get a pull request!

The Internet is not magic and follows physics; the farther away the datacenter; the worse off the results will be. This is why you should probably test with a device that is not your computer, as localhost is local, and you'll be amazed at the speeds to get a crappier one later.

The client must wait for a message, and respond with "recieved". This speed test does not work otherwise. A quick Swift implementation can be seen below.

import Starscream

// ...

socket.onText = { (text: String) in
    // do some validation if needed to just get the speed test
    socket.write(string: "received")
}