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

readahead

v0.2.4

Published

A fast way to sequentially and asynchronously access buffers of any size from a readable.

Downloads

6

Readme

Readahead

A fast way to sequentially and asynchronously access buffers of any size from a readable.

readahead will speed it up, especially if your average requested buffer size is less than 4kb

Usage

// const readahead = require('readahead')
import readahead from 'readahead'
import { createReadStream } from 'fs'

async function main () {
  readable = createReadStream('large-file.data')
  const reader = readahead(readable)
  let length = 100
  while (true) {
    const { value, done } = await reader.next(length)
    if (done) break
    console.log(value) // buffer of size <length>
  }
}
main().catch(console.error)

Benchmark

Execution context: MBP 2015

A 1.6GB pcap file was parsed, segmenting packet header and body. No body decoding.

We compare the reading modes "classic" vs "streaming" vs "idle".

In classic mode, the reader reads the individual buffers as needed, which requires many read operations on the disk. Slowing down the process.

In streaming mode, the reader reads a configurable amount of bytes ahead using fs.createReadStream and caches them in memory. Once the parser wants to access these bytes, they are read from memory directly and the rolling window of cached bytes moves along until the end of the file is reached.

In idle mode, nothing happens besides the file being read using fs.createReadStream. This serves as limit for "how fast it gets with NodeJS".

| mode | duration [s] | compared with idle mode |---------|--------------|--- | idle | 1.164 | 1.0 | stream | 1.538 | 1.3 | classic | 35.405 | 30.4

RAW data

fh.read every buffer:             29.86s user 17.48s system 133% cpu 35.405 total
readStream and readahead parsing:  1.00s user  0.82s system 118% cpu  1.538 total
readStream, no parsing:            0.45s user  0.99s system 124% cpu  1.164 total (idle reference)