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
When doing load testing of the entire solution, including trader, I notice that the trader pod is occasionally killed due to OOM, OOMKilled. The k8s runtime is killing the pod due to the pod more than the maximum amount of memory allowed.
Although adding a memory metric to HPA policy might mask the underlying issue in trader it could be nice to have this as another scaling policy in our toolbox.
The text was updated successfully, but these errors were encountered:
Related to #13.
When doing load testing of the entire solution, including
trader
, I notice that thetrader
pod is occasionally killed due to OOM,OOMKilled
. The k8s runtime is killing the pod due to the pod more than the maximum amount of memory allowed.Although adding a memory metric to HPA policy might mask the underlying issue in
trader
it could be nice to have this as another scaling policy in our toolbox.The text was updated successfully, but these errors were encountered: