You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't have anything other than anecdotal evidence to support this right now, but at high volume lru-cache leaks memory. It's not noticeable on most projects, but on my high volume sites I find that the servers are bleeding memory and require restarts every few hours. This is consistent with any caching modules that uses lru-cache as the underlying mechanism (mongoose-cache, async-cache, etc).
I'm still looking into this and trying to do memory profiling to determine what the bug is. I assume it has something to do with storing complex objects. But I just wanted to give a heads up in case anyone else plans on using this at large scale.
The text was updated successfully, but these errors were encountered:
If you can reproduce it, the easiest way I know to track down the source of a memory leak is to run it on SmartOS, get a core dump with gcore, and then use ::findjsobjects in MDB to find out what is taking up the space.
I don't have anything other than anecdotal evidence to support this right now, but at high volume lru-cache leaks memory. It's not noticeable on most projects, but on my high volume sites I find that the servers are bleeding memory and require restarts every few hours. This is consistent with any caching modules that uses lru-cache as the underlying mechanism (mongoose-cache, async-cache, etc).
I'm still looking into this and trying to do memory profiling to determine what the bug is. I assume it has something to do with storing complex objects. But I just wanted to give a heads up in case anyone else plans on using this at large scale.
The text was updated successfully, but these errors were encountered: