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
I've deployed Dragonfly in a Kubernetes cluster using the Helm chart. I've configured it to proxy a private image registry. Here are my steps:
On a random node, pulling a 1GB image for the first time takes 7 seconds.
In the var/lib/dragonfly directory of dfdaemon, I can see cached task. The monitoring shows the metrics dragonfly_scheduler_traffic with both backtosource and remotepeer traffic types.
After manually executing crictl rmi to remove the test image from the node and pulling again, it takes 4.5 seconds. The dfdaemon logs seem to indicate a cache hit, but the speed remains slow.
I've deployed Dragonfly in a Kubernetes cluster using the Helm chart. I've configured it to proxy a private image registry. Here are my steps:
var/lib/dragonfly
directory of dfdaemon, I can see cached task. The monitoring shows the metricsdragonfly_scheduler_traffic
with bothbacktosource
andremotepeer
traffic types.crictl rmi
to remove the test image from the node and pulling again, it takes 4.5 seconds. The dfdaemon logs seem to indicate a cache hit, but the speed remains slow.the peer log, seems to hit the local cache:
peer.txt
scheduler.txt
seed-peer.txt
My Questions:
My Configuration:
dfdaemon:
Environment:
The text was updated successfully, but these errors were encountered: