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 know that electron apps use a lot of memory to begin with, but I notice that Cerebro helpers use a lot, and I think this plugin may be the culprit. (I use it a lot).
I have been looking into the memoizee library, and notice that there is no default limit on size, nor a default limit on how long to hold things. There is also no way to store the results to disk instead of keeping them in memory. I believe all of this causes Cerebro's memory footprint to grow the more this plugin is used.
Short term, I'd suggest adding some size limits, and time limits.
Long term, I'd suggest looking into different memoize libraries to use that would allow developers to save results to disk instead of holding them in memory.
The text was updated successfully, but these errors were encountered:
@codingmatty I'd say that storing results on disk is not memoization, so we should split these two terms – memoization and caching. In this plugins we only memoize but I agree that we should add some TTL to memoized results.
I know that electron apps use a lot of memory to begin with, but I notice that Cerebro helpers use a lot, and I think this plugin may be the culprit. (I use it a lot).
I have been looking into the
memoizee
library, and notice that there is no default limit on size, nor a default limit on how long to hold things. There is also no way to store the results to disk instead of keeping them in memory. I believe all of this causes Cerebro's memory footprint to grow the more this plugin is used.Short term, I'd suggest adding some size limits, and time limits.
Long term, I'd suggest looking into different memoize libraries to use that would allow developers to save results to disk instead of holding them in memory.
The text was updated successfully, but these errors were encountered: