Replies: 1 comment 1 reply
-
Hi, That is strange. You should not need to release memory. If you can isolate the problem, please open an issue with a reproducible example so we can look into this. cheers, Maarten |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi There,
I have a project running on vaex v4.0.0, I also have it wrapped around flask to have API's running off it. I was hopping to get some help related to memory.
I do face memory leak issues while using group by here's an example.
df.groupby(['rooms_count'], agg={vx.agg.mean('price_per_meter'),vx.agg.min('price_per_meter'),vx.agg.max('price_per_meter'),vx.agg.count('price_per_meter')})
My issue is not with the amount of memory being used. But after the API call is executed the memory used is not released back to the OS. Scale it to multiple API requests and soon I am out of memory on server. I have tried using garbage collection but still the memory isn't released back to the OS.
I would really appreciate if I could get some insight on how to release that memory back once a request is finished. I would love to know if there's something I've been doing wrong which may have caused this issue ?
@maartenbreddels
Beta Was this translation helpful? Give feedback.
All reactions