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

socket-stress-test

v0.1.0

Published

Enables you to create basic stress tests for sockets

Downloads

101

Readme

Socket Load Tests

This is a basic utility that you can use to do a stress test on your Socket IO Server.

Installation

To install this package you can run the following command:

npm install socket-load-tests

Usage

There are two ways to use the stress test. Option one is running it through your desktop, option two is running it through a different server. Here we show you how to use this package (works both for server and client side).

var SocketPromiseHandler = require('socket-stress-test')

socket_handler = new SocketPromiseHandler({
     ioUrl: 'http://your-external-server:3000'
      , connectionInterval: 1000 // Fire one each second
      , maxConnections: 100 // Stop at having 100 connections
      , ioOptions: {
            transports: ['websocket'], // force only websocket (optional)
        }
})


socket_handler.new(function(socketTester, currentConnections) {
        // New connection comes in.
    })
    .disconnect(function(socketTester) {
        // Connection is disconnected by socket
    })
    .addEmit('joinRoom', {
          your: "data"
    }, 200) // after 200
    .addEmit('newMessage', {
        other: "data"

    }, 1000) // After 1000
    .run()

Socket Promise Handler

The socket promis handler is the scheduler which you can use to send new emits. These emits will be distributed at the time each connection is made. All these emits will also be sequenced in a loop afterwards.

addEmit(eventKey, payload, delay)

To add an event you can run addEmit with the eventKey, payload and delay. The delay is the delay after the previous emit.

new(socketTester, currentConnections)

Everytime a new connection is made the new() event callback is getting called.

run()

This is the last thing you want to call before you have set up everything (all the emits etc.)

stop()

This is when you want to stop the stress test.

Configuration

There is some configuration when you create a new SocketPromiseHandler:

  • ioUrl: The Socket Server you want to test
  • maxConnections: How many connection does the stress test go to
  • connectionInterval: The interval of creating a new connection
  • ioOptions: Extra options we put into the socket.io-client

Testing

You can test the project by running the following command in the root folder:

npm test

Note: Testing has Dev dependencies, make sure those are installed.