mirror of https://github.com/BOINC/boinc.git
A tiny bit of documentation
svn path=/trunk/boinc/; revision=12608
This commit is contained in:
parent
8b6576a549
commit
56fd688f54
|
@ -0,0 +1,22 @@
|
|||
-----------------
|
||||
Setting it all up
|
||||
-----------------
|
||||
The .torrent cache will need to know where to look for the files that are going
|
||||
to be sent to the clients. Usually this will be the project download directory.
|
||||
|
||||
<insert more settings here>
|
||||
|
||||
------------------
|
||||
How to enable this
|
||||
------------------
|
||||
By default Bittorrent support is turned off on both server and client. You must
|
||||
enable bittorrent in your server configuration files by doing this:
|
||||
|
||||
<insert useful guide here>
|
||||
|
||||
You must also convince your users that enabling Bittorrent support on their clients
|
||||
is a useful way to help the project. It is a good idea to let them know that
|
||||
setting the "Maximum upload rate" under general preferences enables them to
|
||||
control just how much of their outgoing bandwidth is ever used. A setting of 70%
|
||||
or less of their actual bandwidth is recommended to avoid creating latency issues
|
||||
on their connection.
|
|
@ -0,0 +1,43 @@
|
|||
-----------------------------------
|
||||
Bittorrent file distribution system
|
||||
-----------------------------------
|
||||
When several workunits require the same file (for instance any particularly big
|
||||
application file) it is really a waste to use a central server to distribute this
|
||||
file. First of all a central server requires lots of bandwidth - which may be
|
||||
quite expensive. Secondly getting 10'000 requests for the same multi-megabyte
|
||||
file may be too much for even the largest of servers.
|
||||
|
||||
The solution is to harness the power of peer-to-peer computing in the domain of
|
||||
volunteer and desktop grid computing by allowing the clients to share pieces of the
|
||||
files they are downloading.
|
||||
|
||||
How it works
|
||||
------------
|
||||
Since noone can be trusted, "Bob" (a client) will need some way of knowing if "Eve"
|
||||
(another client) sent him a valid piece of the original file. To enable him to do
|
||||
so Bob has downloaded a .torrent from the project servers. The .torrent describes
|
||||
the file he is downloading; it contains hash values for each piece so that he can
|
||||
check whether "Eve" is trying to cheat him.
|
||||
|
||||
If "Alice" also wants to download the same file as "Bob" they can each fetch a
|
||||
different piece from the project servers and then share the pieces. Seen from
|
||||
"Bob" and "Alice"'s perspective this potentially doubles the download rate (if you
|
||||
see it from the project perspective it cuts the required network bandwidth in half).
|
||||
As more people join the synergetic effect increases dramatically.
|
||||
|
||||
Isn't Bittorrent illegal?
|
||||
-------------------------
|
||||
Bittorrent is a protocol for sharing files across the internet. As such it cannot
|
||||
be illegal in itself - it is what you do with it that matters.
|
||||
If you take a look at all the filesharing protocols out there Bittorrent seems to
|
||||
be the one that has been taken into widespread use in the whitehat part of the
|
||||
internet. Several major companies, including the movie industry, have adopted the
|
||||
technology because of its unique ability to distribute load. To name a few uses:
|
||||
- Bittorrent.com (Works with the movie industry, sells movies and shows)
|
||||
- Blizzard Entertainment (Uses BT to distribute data patches for their World of
|
||||
Warcraft game)
|
||||
- EletricSheep screensaver (Uses BT to distribute computed "dreams")
|
||||
|
||||
How do I enable this?
|
||||
---------------------
|
||||
Have a look at the INSTALL file located in the same directory as this file.
|
Loading…
Reference in New Issue