-
I am using dragonfly helm chart with resources restrictions. resources:
limits:
cpu: "1000m"
memory: "512Mi"
requests:
cpu: "500m"
memory: "256Mi" But I see that the dragonfly itself selects the resource parameters. This can lead to ooms, high CPU consumption (throttling).
How to correctly determine memory and number of threads for dragonfly to be good? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 11 replies
-
Dragonfly should automatically determine whether it is running inside a container (CGroup), this was introduced here. Running using docker-compose seems to work fine, so this might be an issue with Helm/Kube |
Beta Was this translation helpful? Give feedback.
-
I don't know C++ well, but I'll try to figure it out. I would be grateful for any help :)
|
Beta Was this translation helpful? Give feedback.
-
@Letfdsada you can also manually override resource reservation by passing |
Beta Was this translation helpful? Give feedback.
Yup, upgrading to Linux kernel 5.8 (or newer) would solve the issue for now.
Maybe on another day Dragonfly will support v1 detection as well, but for now upgrading will work.
Edit: Dragonfly now supports cgroup v1 as well. This was pushed in PR #1329, and should be available within v1.4. 😄