Arvid Norberg
Arvid Norberg
it would be helpful if someone experiencing this would examine the file (e.g. the number of extents) to try to understand why it's using so much space, and reporting back...
is this using libtorrent 1.2.x? If so, the [read_cache_line_size](http://libtorrent.org/reference-Settings.html#read_cache_line_size) setting could be lowered. If this is using libtorrent 2.0.x, the read-ahead is a kernel setting.
how does one identify a temporary IPv6 address? I assume it's a flag on the interface. my understanding is that `IFF_DYNAMIC` means it was configured by DHCP, but maybe this...
> i'm a dev myself I'm sure patches are welcome
it's explained under the "building" heading in the [readme](https://github.com/bittorrent/bootstrap-dht/blob/master/README.rst).
would it be reasonable to only announce stats to the v2 info-hash, if it's a v2 torrent?
> @arvidn hybrid torrents are the concern here. In that case you want to announce both to get peer lists for both. I suggested announcing *stats* to the v2 hash,...
was there any resolution on this? I think status quo is to announce every listen socket (e.g. IPv4 and IPv6) and one for each bittorrent version the torrent participates in...
> This sounds like a bunch of announces for each torrent, some trackers with a lot of traffic could literally be hammered. If you have both an IPv6 and IPv4...
I also meant to say: I think status quo is option (b). It would be possible to implement (a), with some complexity and some additional space requirements.