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

@raydiant/device-events-client

v0.1.3

Published

Client for shipping Raydiant device events

Downloads

11

Readme

device-events-client

Client for shipping device events

Offline storage

Each event is estimated around 700 bytes.

Assuming one playback start/stop (2 events) every 15 seconds, in one hour we will have 480 events.

Given this, the default retry buffer size is 500 events to roughly fit 1hr of playback into the buffer.

The storage write queue is 24 to roughly fit 1 day of playback into memory before being written to disk.

The storage max count is 400 to fit well over over 2 weeks of playback data onto disk (336).

The expected mem/disk usage is:

  • retry buffer: 500 events * 700 bytes = 350KB mem
  • storage write queue: 24 * 500 * 700 = 8.4MB mem
  • storage max count: 400 * 500 * 700 = 140MB disk