Reuse typed arrays

npm install typedarray-pool
6 downloads in the last day
30 downloads in the last week
103 downloads in the last month


A global pool for typed arrays.


var pool = require("typedarray-pool")

//Allocate a buffer with at least 128 floats
var f = pool.malloc(128, "float")

// ... do stuff ...

//When done, release buffer


npm install typedarray-pool


var pool = require("typedarray-pool")

pool.malloc(n[, dtype])

Allocates a typed array (or ArrayBuffer) with at least n elements.

  • n is the number of elements in the array
  • dtype is the data type of the array to allocate. Must be one of:

    • "uint8"
    • "uint16"
    • "uint32"
    • "int8"
    • "int16"
    • "int32"
    • "float"
    • "float32"
    • "double"
    • "float64"
    • "uint8_clamped"
    • "buffer"

Returns A typed array with at least n elements in it.

Note You can avoid the dispatch by directly calling one of the following methods:

  • pool.mallocUint8
  • pool.mallocUint16
  • pool.mallocUint32
  • pool.mallocInt8
  • pool.mallocInt16
  • pool.mallocInt32
  • pool.mallocFloat
  • pool.mallocDouble
  • pool.mallocArrayBuffer
  • pool.mallocUint8Clamped
  • pool.mallocBuffer


Returns the array back to the pool.

  • array The array object to return to the pool.

Note You can speed up the method if you know the type of array before hand by calling one of the following:

  • pool.freeUint8
  • pool.freeUint16
  • pool.freeUint32
  • pool.freeInt8
  • pool.freeInt16
  • pool.freeInt32
  • pool.freeFloat
  • pool.freeDouble
  • pool.freeArrayBuffer
  • pool.freeUint8Clamped
  • pool.freeBuffer


Removes all references to cached arrays. Use this when you are done with the pool to return all the cached memory to the garbage collector.


Why cache typed arrays?

Creating typed arrays is stupidly expensive in most JS engines. So it makes sense to pool them, both so that frequently used typed arrays stay hot in cache and so that you can avoid having to trigger some expensive realloc operation whenever you use them.

Why not cache ArrayBuffers instead?

Because creating a typed array from an array buffer is almost as expensive as allocating the typed array in the first place. While this approach would save memory, it doesn't give much of a performance benefit for small arrays. (See for example this experiment:


Is this library safe to use?

Only if you know what you are doing. This library will create a global pool of typed array buffers that you can use across many modules. The downside though is that you have to manage all the memory yourself, so you can easily shoot yourself in the foot if you screw up.


(c) 2014 Mikola Lysenko. MIT License

npm loves you