Replies: 3 comments
-
you have to use memory leak tool to find out the leaking objects/roots of that |
Beta Was this translation helpful? Give feedback.
0 replies
-
Can you try profiling with memray to see where the memory leak is coming from? |
Beta Was this translation helpful? Give feedback.
0 replies
-
We're seeing a similar issue. See this comment. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Recently we upgrade from celery 4.4.3 to 5.3.4 in order to overcome a memory leak issue we were experiencing.
After that we see there's a minimum change about ram consumption but anyway the workers still consuming ram even when no task are executed.
This is the ram memory consumption from one of the workers, from 15 to 18 there were no task executed, anyway the worker is consuming memory.
We are using celery 5.3.4 and python 3.9.0.
Someone have experience this same issue? how do you fix it?
Beta Was this translation helpful? Give feedback.
All reactions