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

object-object-pool

v1.0.0

Published

A class to help manually manage object memory in JavaScript

Downloads

6

Readme

Object Object Pool

Build Status

A manual memory management tool for JavaScript.

Why?

Sometimes you have a lot of objects. Sometimes having those garbage collect causes some sawtooth ugliness ugly sawtooth memory allocation in chrome devtools

OK but why is this bad?

Garbage collection can be slow, especially if you're working with a lot of objects. Sometimes it is better to allocate a bunch of objects you need and just reuse them. see this dope article

API

The API for this is fairly simple and straight forward. You have an alloc() method, a free(object) method, and a collect() method available.

constructor

the constructor for an ObjectPool has an optional number of objects you can give it. If you pass a number, it will preallocate that many objects.

let pool = new ObjectPool();
console.log(pool.status.totalAllocated);
// 0

let poolPreAlloc = new ObjectPool(5);
console.log(pool.status.totalAllocated);
// 5

The following all assume you have created an object pool.

let pool = new ObjectPool();

alloc()

This will assign myObject to be {}. You can use this object as you wish. When you are done with this obect you can free it.

console.log(pool.status.totalAllocated)
// 0

let myObject = pool.alloc();
// {}
console.log(pool.status.totalAllocated)
// 1
console.log(pool.status.totalFree)
// 0

free()

When you are finished with an object, calling pool.free(object) will mark it as free to use again. When you do this, you should also mark your reference to the object as null.

let myObject = pool.alloc();
// {}
console.log(pool.status.totalAllocated)
// 1
console.log(pool.status.totalFree)
// 0
pool.free(myObject); // internally recycles object
myObject = null;
console.log(pool.status.totalAllocated)
// 1
console.log(pool.status.totalFree)
// 1

collect()

collect() will remove all unused objects from your pool. If you have allocated 5 objects, and one is in use, internally you will have one allocated object and zero free objects.

let objectOne = pool.alloc();
let objectTwo = pool.alloc();

pool.free(objectTwo); // internally recycles object
objectTwo = null;

console.log(pool.status.totalAllocated)
// 1
console.log(pool.status.totalFree)
// 0