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

timeoutengine

v0.1.0

Published

Simple node module to find the 99%ile timeout value.

Downloads

3

Readme

node-timeoutengine

Simple node module to find the 99%ile timeout value.

var wreck = require('wreck');
var timeoutengine = require('timeoutengine');


var defaultTimeout = 5000;
var serviceName = 'httpbin_get';

 function makeServiceCall(callback) {
    var options = {
        timeout: timeoutengine.getSocketTimeout(serviceName) || defaultTimeout
    };
    var reqStart = Date.now();
    var req = wreck.get('http://httpbin.org/get', options, function (err, response, payload) {

        timeoutengine.addSocketDuration(serviceName, Date.now() - reqStart);    //pumping the socket duration

        if (!err && response && response.statusCode === 200 && payload) {
            //console.log(payload.toString());
            // do something this payload
        }
        callback();
    });
}

Problem statement

I am making a service call from node and hardcoding a fixed socketTimeout (or connectTimeout) value for the same. I am not sure that is the ideal value I can use?

TimeoutEngine

TimeoutEngine has API to feed the connect/socket durations and after let say N (default 100) request start returning the 99%ile + delta value. This is useful if you need adaptive timeout value based on the current server/network conditions.

API

  • configure(options) - [Optional] Use if you want a different default config.
  • addDuration(key, value) - Generic addDuration API
  • getTimeout(key) - Generic getTimeout API
  • addConnectDuration(key, value) - Call this API to feed the connect duration of a service call for successful as well as failed requests.
  • addSocketDuration(key, value) - Call this API to feed the socket duration of a service call for successful as well as failed requests.
  • getConnectTimeout(key) - Returns this 99%ile + delta connect Timeout value
  • getSocketTimeout(key) - Returns this 99%ile + delta socket Timeout value