-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
name resolve takes exactly 1 minute and loses cache after 30 seconds #6800
Comments
Hi Mark, At the moment IPNS is quite slow, because there are some issues with the IPFS DHT. Basically what's happening is that it tries to fetch a certain minimum number of records from the DHT but times out (after one minute) before it's able to get all of them, so it returns the best of the records that it was able to find. There are some suggested work-arounds in this thread. The good news is that we are very actively working on fixing the DHT slowness, and expecting a release candidate in the next few weeks that should improve things a lot. You can track our progress in this issue |
Hi,
The obligatory version information:
Now this site is a playground site with only pinata and a digitalocean server backing it. The timing of a resolve:
Right after that resolve it works fast for, say, about 30 seconds or so.
Then it again needs to resolve and, and this really surprises me, takes again exactly 1 minute!
See:
You'd think i copied and pasted the two timings from above, but they were really this EXACT in time.
That's no coincidence!
Something somewhere in the IPFS code that does name resolving is set at 1 minute. Or there are some timers or delays adding up to a total of 1 minute sharp.
I don't think my DNS record is wrong.
I think there are 2 issues here.
Is there any additional information that i can provide to help tracking this?
Cheers,
Mark
To amend, this has likely been reported a lot before. I couldn't find github issues, but did find this thread on the forum: https://discuss.ipfs.io/t/why-ipns-is-so-slow/2161
The text was updated successfully, but these errors were encountered: