Métriques du dépôt
- Stars
- (13 906 stars)
- Métriques de merge PR
- (Merge moyen 4j 2h) (28 PRs mergées en 30 j)
Description
I investigated a bit a performance issue - where it takes quite a long time before data behind an IPNS record can be resolved via the DHT.
It seems that the newly added content is too large, so there's a large backlog of newly added pins and MFS data on the node, that it is able to push the CID for the name record in a reasonable amount of time.
A dedicated ipfs dht provide <CID> before running ipfs name publish --key=<keyID> <CID> solved this issue for me.
So there seems to be an improvement opportunity:
If the CID which should be published as a name record is still somewhere on the queue for sending it to the DHT as provider IPFS could give this CID priority, that it will be the next CID to be published. This way ipfs makes rue that the new name record will be resolvable via DHT.