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

scale.io

v1.1.0

Published

loadbalancing and autoscaling for websocket based EC2 cluster.

Downloads

4

Readme

scale.io

loadbalancing and autoscaling module for websocket based EC2 cluster without ELB.

architecture

  • no ELB

architecture

  • slack based monitoring

monitoring1

monitoring2

  • zero downtime deploy
  • multi-AZ based
  • auto fail over

how to use

scale.js

require('scale.io');

set config yml file

set config/default.yaml or config/env.yaml your main app.

Example is this.

execute

node --harmony scale.js

config details

conf for redis / aws / slack

enter your

  • redis host & port
  • access key id, secret access key and region
  • slack info

conf for loadbalancing / autoscaling / monitoring

enter some info (details are below).

conf for loadbalancing

Correspond to A and B in above structure chart.

|key|desc| |---|---| |timeoutThresholdForRedHost|Getting no response within this value(ms), host is regard as RedHost(=DyingHost).| |connNumForRedHost|RedHost is expressed by this value at loadbalancing log.| |ec2HostTagKey|EC2 tag key| |ec2HostTagValueForLobby|EC2 tag value for lobby server.| |ec2HostTagValueForGame|EC2 tag value for game server.| |intervalForAutoscalingSec|cycle time of autoscale watching process| |intervalForHostInfoUpdateSec|cycle time of loadbalancing process| |redisKeyForLobbyLoadbalancing|redis key name for lobby loadbalance.| |redisKeyForGameLoadbalancing|redis key name for game loadbalance.|

conf for autoscaling

Correspond to C in above structure chart.

|key|desc| |---|---| |cfnStackName|stack name of cloudformation.| |serverTypeNum|server type number. if you use lobby and game, enter 2.| |scaleOutThreshold|average connection number of instances for scale out.| |scaleInThreshold|average connection number of instances for scale in.| |cfnUpdateCmd|update cloudformation command.| |minimumGreenHostsNum|falling below this value, scale out starts.| |forceScaleOutStartAt|scale out forced to start after this time.| |forceScaleOutEndAt|scale out forced to start before this time.| |scaleInAvailableStartAt|scale in can be started after this time.| |scaleInAvailableEndAt|scale in can be started after this time.| |notifyRoomNumMessage|notifying message by slack.| |scaleInMinimumIntervalSec|scale in can be started countinuously after this interval.| |scaleOutMinimumIntervalSec|scale out can be started countinuously after this interval.| |specifiedTimeGreenHostsNum|instance number will be change to this value between specified time.| |restartCmd|restart autoscale process commond.| |autoRestartCpuUsageThresholdForLB|if cpu usage exceed this value, process restart.| |autoRestartMonitorIntervalSec|monitoring span for auto restart.|

conf for monitor

Correspond to D in above structure chart.

|key|desc| |---|---| |monitoredHost|monitored target.| |monitoredProcess|like 'game', 'lobby'| |monitoringIntervalSec|monitoring span| |decisionIntervalSec|monitored process does not reply throughout this span, it is regard as died.|