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 160MB image for the first time takes 10 seconds.
In the var/lib/dragonfly directory of dfdaemon, I can see cached pieces. 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 still takes 10 seconds. The dfdaemon logs seem to indicate a cache hit, but the speed remains slow.
Monitoring data again shows no local_peer traffic type in metrics dragonfly_scheduler_traffic.
the dfdaemon log, seems to hit the local cache:
My Questions:
Why is the pull speed slow despite hitting the cache? It doesn’t differ much from pulling directly.
Does the dragonfly_scheduler_traffic metric collect local_peer traffic? Or is there another metric to monitor local_peer traffic? (I noticed the Rust version of the client exposes related metrics.)
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 pieces. 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 still takes 10 seconds. The dfdaemon logs seem to indicate a cache hit, but the speed remains slow.local_peer
traffic type in metricsdragonfly_scheduler_traffic
.the dfdaemon log, seems to hit the local cache:
My Questions:
dragonfly_scheduler_traffic
metric collectlocal_peer
traffic? Or is there another metric to monitorlocal_peer
traffic? (I noticed the Rust version of the client exposes related metrics.)My Configuration:
dfdaemon:
Environment:
The text was updated successfully, but these errors were encountered: