Takes long time to cache (set&get) large JSON objects about node-cache

[LiveGood]

When creating an instance of the cache this should help:
myCache.options.useClones = false;

By default node-cache creates deep clones of each object you set, so a large object will take much longer to be deep cloned than a large string.
Take in mind that if you set this option to false, if for some reason you need to store the same object twice under different keys, both objects will have the same reference, and change in one will affect the other.
You can avoid this by doing the deep cloning yourself when needed.

[matys1]

@LiveGood thanks, this helped with my issue. Was querying 125k rows over 4 columns and it would take 11s to return from cache (slower than if I would query API directly). After turning this to false it's getting it from cache in <500ms.