Occasionally try to find additional providers even if we already have them.

[Stebalien]

Currently, once we've found at least one peer providing blocks for us, we stop looking no matter how slow that peer is. Instead of settling, we should occasionally search for better providers.

[hoogw]

Good, without this feature, it always load from my home(very slow) computer.
Even my work computer (very fast) is available.

Now I have to completely shut down home computer to force it choose my work computer.

Try my sample:
https://transparentgov.net/json2tree/ipfsList.html

Another problem I found is:
For large 277GB, ( click 'Los Angeles County Land Records' ), it extremely slow, specially more level of sub-folder, you are more likely to get 505 time out error, 524 time-out,

For only 0-1 level sub-folder , it is fast, and not likely fail. (Other than Los Angeles)

[hoogw]

My workplace node (upload 800Mbps), my home(upload 10Mbps) node.
Both host the same content.
https://transparentgov.net/json2tree/ipfsList.html

slow node always been used, even the fast node available.
I want to use fast node first.
Can I specify the fast(high bandwidth) node have higher priority?

I try: ipfs dht provide ...

But it does not work.

What this command really does?
Does it inform IPFS that, my node provide this ?

How to set node with higher priority for specific ?

[Stebalien]

You can't.

[hannahhoward]

This makes sense. There's also the issue of occasionally broadcasting to see if there are faster peers among those you've found.

Much of this is covered in the next round of session speedup (though not the occasionally finding providers part, which makes sense -- we oughta add that one, and it'd be an easy change)