| 1 |
[[meta title="apt-p2p 0.1.3: now faster"]]
|
| 2 |
|
| 3 |
I have updated [apt-p2p][10] to version 0.1.3, which is available now in
|
| 4 |
unstable and [my repository][20] (see my [[previous post|May-04-2008]]
|
| 5 |
introducing apt-p2p).
|
| 6 |
|
| 7 |
This update brings mostly speed improvements to finding peers to
|
| 8 |
download from, and performing the download. Nodes in the DHT are now
|
| 9 |
checked for responsiveness more thoroughly before adding them to the
|
| 10 |
routing table, and rechecked more frequently afterwards. This should
|
| 11 |
prevent bad nodes from propagating through the system, and departing
|
| 12 |
nodes remaining in the system long after they have left. Downloading
|
| 13 |
from peers is also quicker, as bad peers are dropped with a quicker
|
| 14 |
timeout value and after a small number of errors. [There was also a
|
| 15 |
bug][30] revealed by about 10% of the mirrors that caused downloads to
|
| 16 |
fail, and was fixed in version 0.1.2.
|
| 17 |
|
| 18 |
This update is STRONGLY recommended, as keeping unresponsive nodes out
|
| 19 |
of the DHT will make everyone's experience better. If you tried apt-p2p
|
| 20 |
and had some problems, I hope you'll consider trying again now.
|
| 21 |
Unfortunately, these are enhancements I could not predict needing before
|
| 22 |
releasing to the public, as the problems they solve are all caused by
|
| 23 |
having a larger number of users, some of which are unresponsive.
|
| 24 |
|
| 25 |
There are still a large number of peers (maybe 50% of them) that are
|
| 26 |
unreachable, and so can not share any files with other peers. I don't
|
| 27 |
have a good way to check yet, but you can go to sites such as [this
|
| 28 |
one][40] to probe your client for you. Just enter the remote IP address
|
| 29 |
and port (available on the [status page][50]) of your client in the form
|
| 30 |
`http://ipaddress:port/` (e.g. `http://1.2.3.4:9977/`). If the check
|
| 31 |
returns any HTTP headers (even a 404 Not Found response) then you're
|
| 32 |
fine, but if it doesn't return anything then your peer is firewalled or
|
| 33 |
NATted and [should probably be fixed][60].
|
| 34 |
|
| 35 |
Here are the changelog entries for 0.1.2 and 0.1.3:
|
| 36 |
|
| 37 |
* Speed up downloading from peers
|
| 38 |
- Set a new peer's ranking values so they don't get an unfair
|
| 39 |
advantage.
|
| 40 |
- Reduce the HTTP connection timeout to 10s.
|
| 41 |
- Drop peers after a limited number of errors.
|
| 42 |
* Speed up the DHT requests when nodes fail
|
| 43 |
- Schedule a re-ping message after adding a new node.
|
| 44 |
- When a node fails, schedule a future ping to check again.
|
| 45 |
- Send periodic finds to nodes that are stale.
|
| 46 |
- Increase the stored value redundancy to 6.
|
| 47 |
- Increase the concurrency of DHT requests to 8.
|
| 48 |
- Add early termination and ignoring slow responses to
|
| 49 |
recursive DHT actions when timeouts occur.
|
| 50 |
* Remove the debconf note about port forwarding (Closes:[#479492][70])
|
| 51 |
- Add a NEWS entry for port forwarding
|
| 52 |
* Fixed a bug in the HTTP downloader that caused errors with some
|
| 53 |
mirrors that always close the connections (Closes: [#479455][30])
|
| 54 |
|
| 55 |
[10]: http://www.camrdale.org/apt-p2p.html
|
| 56 |
[20]: http://debian.camrdale.org/
|
| 57 |
[30]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479455
|
| 58 |
[40]: http://webtools.live2support.com/header.php
|
| 59 |
[50]: http://localhost:9977/
|
| 60 |
[60]: http://portforward.com/
|
| 61 |
[70]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479492
|
| 62 |
|
| 63 |
[[tag debian apt-p2p]]
|
Parent Directory
| 
Revision Log