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 🙏

© 2025 – Pkg Stats / Ryan Hefner

bench-flumelog

v2.0.0

Published

a simple benchmark of flumedb log implementations.

Readme

bench-flumelog

a simple benchmark of flumedb log implementations.

method

append as many items as can be added in 10 seconds, then stream all items, then read out those items randomly.

for each phase, record the number of items per second, and the mb/second.

results

flumelog-offset

name, ops/second, mb/second, ops, total-mb, seconds
append, 109777.644, 13.881, 1097996, 138.844, 10.002
stream, 105121.787, 13.292, 1051323, 132.942, 10.001
random, 26169.883, 3.309, 261725, 33.095, 10.001

flumelog-level

name, ops/second, mb/second, ops, total-mb, seconds
append, 64168.894, 8.116, 643229, 81.359, 10.024
stream, 69560.83, 8.798, 643229, 81.359, 9.247
random, 31589.041, 3.995, 315922, 39.959, 10.001

flumelog-memory

memory is extremely fast, because it's kept completely in memory.

name, ops/second, mb/second, ops, total-mb, seconds
append, 121065.388, 15.313, 1212712, 153.391, 10.017
stream, 247025.213, 574.498, 1212712, 153.391, 0.267
random, 662146.485, 83.752, -1967807.592, 837.605, 10.001

stream reads more per second but only the same total number of mb, because stream stops once it has read the entire log, but random continues for 10 seconds.

flumelog-idb

these tests on lenovo x201

(firefox)

name, ops/second, mb/second, ops, total-mb, seconds

append, 7738.949, 0.979, 81940, 10.366, 10.588
stream, 2996.709, 0.379, 30054, 3.802, 10.029
random, 4072.355, 0.515, 40805, 5.162, 10.02

(electron/chromium)

name, ops/second, mb/second, ops, total-mb, seconds
append, 6179.487, 0.782, 65552, 8.295, 10.608
stream, 3189.681, 0.403, 31900, 4.037, 10.001
random, 5695.873, 0.72, 57010, 7.215, 10.009

something about indexed db is making this very slow!


these runs on Samsung J2, which was the cheapest "smart" phone I could purchase at my local shop, for $220 NZD. (~158 USD)

(mobile chrome, samsung J2)

name, ops/second, mb/second, ops, total-mb, seconds
append, 1884.024, 0.238, 20485, 2.591, 10.873
stream, 839.716, 0.106, 8398, 1.062, 10.001
random, 1060.481, 0.134, 10608, 1.341, 10.003

(mobile firefox, samsung J2)

name, ops/second, mb/second, ops, total-mb, seconds
append, 2273.374, 0.287, 24582, 3.11, 10.813
stream, 1002.299, 0.126, 10025, 1.268, 10.002
random, 1253.374, 0.158, 12535, 1.586, 10.001

mobile is 3-4 times slower.