Publication
Partagez vos connaissances.
Inconsistencies in Kubo DAG Retrieval Time
When using Kubo code for DAG retrieval, I've noticed significant variations in retrieval times, ranging from 2 seconds to a minute for different files. Any insights on what might be causing this discrepancy and how to perform a more in-depth analysis? Are there specific tools or methods to trace and identify the root cause?
- Kubo
Réponses
1You can use tracing code to dig deeper. Start Jaeger with:
docker run -d --name jaeger -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 -p 5775:5775/udp -p 6831:6831/udp -p 6832:6832/udp -p 5778:5778 -p 16686:16686 -p 14268:14268 -p 14269:14269 -p 14250:14250 -p 9411:9411 jaegertracing/all-in-one
Initiate tracing and IPFS daemon with:
export OTEL_TRACES_EXPORTER=jaeger
ipfs daemon
In another shell, execute the following commands:
export OTEL_TRACES_EXPORTER=jaeger
ipfs dag get Qmfoo
Navigate to http://localhost:16686/, filter for cmds.dag.get in the Operation, and analyze the traces to identify potential bottlenecks or issues causing the time discrepancies.
Connaissez-vous la réponse ?
Veuillez vous connecter et la partager.
The InterPlanetary File System (IPFS) is a protocol, hypermedia and file sharing peer-to-peer network for storing and sharing data in a distributed file system.
Gagne ta part de 1000 Sui
Gagne des points de réputation et obtiens des récompenses pour avoir aidé la communauté Sui à se développer.