I highly recommend you not use node-lru-cache: https://github.com/isaacs/node-lru-cache/issues/63 https://github.com/isaacs/node-lru-cache/issues/63 (as you can

I highly recommend you not use node-lru-cache: https://github.com/isaacs/node-lru-cache/issues/63 https://github.com/isaacs/node-lru-cache/issues/63 (as you can see from the last comment on that bug, these truly bizarre performance characteristics were not solved, and I would recommend drop-in replacing the fast-lru library we use).