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
With my current data and code setup, a portfolio.stats call to one of my portfolio takes more than 1GB, however the return value of the stats call takes only 0.02GB.
I guess it's because there is some caching by the stats method under the hood. If it's the issue, is there a way to disable such caching, I don't see why I would need it. I have to run the stats call on multiple portfolios so even with large amount of memory, I'm quickly limited.
Thanks you btw, great tool 👍
The text was updated successfully, but these errors were encountered:
shaft3796
changed the title
Portfolio.stats consume large amount of memory.
Portfolio.stats consumes large amount of memory.
Apr 25, 2024
I found workaround consisting of running the .stats call in a separate process, getting the result using a queue and killing the process. I can now get the result of .stats call without the +1GB memory still allocated.
But let's be honest, this is not the cleanest code I have wrote 😅
With my current data and code setup, a portfolio.stats call to one of my portfolio takes more than 1GB, however the return value of the stats call takes only 0.02GB.
I guess it's because there is some caching by the stats method under the hood. If it's the issue, is there a way to disable such caching, I don't see why I would need it. I have to run the stats call on multiple portfolios so even with large amount of memory, I'm quickly limited.
Thanks you btw, great tool 👍
The text was updated successfully, but these errors were encountered: