ipns resolve local name very slow

[krl]

$ time ipfs name resolve
/ipfs/QmXQ5czKP2mhQrF2RtfiVv9sQ97MpWiyhSTTXgefgQdmHU
real    1m0.097s

@whyrusleeping
This should probably read from the local known value of the ipns key, no?

It was pretty much instant before.

[whyrusleeping]

yeah, this behaviour was changed to query the network for records and select the best one. I agree that resolving the local name should be quick, but i'm not sure on the UX for this.

[jbenet]

wow, is it really taking 1min to go through the whole dht? exhausting the queriable set should exit this quicker.

maybe the queries are taking a long time as setting up new connections is very slow.

we should really get more data + viz on this. i think being able to animate queries and explore them will give us a much better way to solve the problem.

i'm reminded yet again that packet switching replaced line switching.

[whyrusleeping]

@jbenet its mostly dialing stuff that takes lots of time. I was going to work on some little tools for requesting records, giving the ability to specify how many to wait for and other such tweaks.

[krl]

If a quickfix would be possible, that would be great. the --local arg as
you suggested would work. I'm blocked on this re starlog at the
moment.

[whyrusleeping]

@krl i will try and get to that ASAP.

[whyrusleeping]

@krl #1834

[jbenet]

#1834 is merged.