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

zipkin-instrumentation-node-redis

v1.4.0

Published

More up-to date version of the node-redis instrumentation

Downloads

361

Readme

zipkin-instrumentation-node-redis

Node.js CI codecov

This is a small experimental re-write of the original zipkin-instrumentation-redis

This library will wrap the now redis V4 client

Installation

For the new promises based node-redis

npm install zipkin-instrumentation-node-redis

For the <=v3.1 node-redis

npm install zipkin-instrumentation-node-redis@legacy

Usage

(async () => {
  const { Tracer, ExplicitContext, ConsoleRecorder } = require('zipkin')

  const tracer = new Tracer({
    ctxImpl: new ExplicitContext(), // implicit in-process context
    recorder: new ConsoleRecorder(), // batched http recorder
    localServiceName: 'tester' // name of this application
  });
  
  const client = require('zipkin-instrumentation-node-redis')({ tracer })()
  await client.connect();

  const results = await client.set('key', 'value')

  console.log(results) // OK

  await client.quit()
})()

Replacing redis

Please note that due the new version is not a straight swap like @legacy

  1. Replace the imports and .createClient() call
- const redis = require('redis');
- const client = redis.createClient();
+ const createClient = require('zipkin-instrumentation-node-redis')({ tracer })
+ const client = createClient()
  1. Use the client
await client.connect();
...

Benchmark

Due to the proxying nature of the way zipkin works there is a slight discrepancy with performance.

In this case zipkin was faster but not by much

Function calling time:

$ node ./test/benchmark.js
redis             10,457 ops/sec
zipkin/redis      11,532 ops/sec

The space in node_modules including sub-dependencies:

New redis is now exponentially larger than the older version

$ node ./test/size.js
redis@next                                 2560 KB
zipkin-instrumentation-node-redis          2560 KB
zipkin-instrumentation-node-redis@legacy   400 KB
zipkin-instrumentation-redis               724 KB

Test configuration:

$ uname -a
Darwin 2015-MBP 19.6.0 Darwin Kernel Version 19.6.0: <DATE> x86_64
$ node --version
v16.2.0