Metadata gathering speedup question about bittorrent-dht HOT 2 CLOSED

For 1), from the readme:

arr = dht.toArray()

Returns the nodes in the DHT as an array. This is useful for persisting the DHT
to disk between restarts of a BitTorrent client (as recommended by the spec). Each node in the array is an object with id (hex string) and addr (string) properties.

To restore the DHT nodes when instantiating a new DHT object, simply pass in the array as the value of the bootstrap option.

var dht1 = new DHT()

// some time passes ...

// destroy the dht
var arr = dht1.toArray()
dht1.destroy()

// some time passes ...

// initialize a new dht with the same routing table as the first
var dht2 = new DHT({ bootstrap: arr })

from bittorrent-dht.

For 2), you can take some of the peers from the tracker and try adding them to the DHT:

dht.addNode(addr, [nodeId])

Manually add a node to the DHT routing table. If there is space in the routing table (or
an unresponsive node can be evicted to make space), the node will be added. If not, the
node will not be added. This is useful to call when a peer wire sends a PORT message to
share their DHT port.

If nodeId is undefined, then the peer will be pinged to learn their node id. If the peer does not respond, the will not be added to the routing table.

However, there's a issue right now where nodeId is actually required, and you obviously won't know that in advance, since "dht node id" is different from "bittorrent peer id". Issue is open here: #26 PR welcome :)

from bittorrent-dht.