Hello,
I've recently noticed that my mktxp deployed using docker with some memory limits was maxing out the authorized memory limits. After a quick check and knowing that I've recently added new devices, I've decided to give it a little bit more room.
It seemed to work well at first but I can see on the metrics exposed by cAdvisor that the container memory curve is aiming to the moon:
Do you have an idea what could cause that? What can I do to help gather more info on this issue? Maybe it's a python option that reduce the GC frequency until the max allocated memory is reached? (the container is working well even when it reaches the maximum available memory)
Hello,
I've recently noticed that my mktxp deployed using docker with some memory limits was maxing out the authorized memory limits. After a quick check and knowing that I've recently added new devices, I've decided to give it a little bit more room.
It seemed to work well at first but I can see on the metrics exposed by cAdvisor that the container memory curve is aiming to the moon:
Do you have an idea what could cause that? What can I do to help gather more info on this issue? Maybe it's a python option that reduce the GC frequency until the max allocated memory is reached? (the container is working well even when it reaches the maximum available memory)