Hey is it possible to - or is this feature already available?:
Have Bitcomet on multiple computers running the same torrent download and as it downloads splits the file in 2 parts across the 2 computers and then recombines the torrent files after (completion or as it downloads) together using a local connection/wifi? I say this because ive had bitcomet downloading the same torrent on two separate computers (both computers have customized settings + port forwarded for bitcomet) and had different downloading/uploading speed on both and no matter what i do i dont use up my bandwidth tube.
I’m assuming that the majority of newer connections these days have many gigabytes available with fast speeds 5mbps+. If you split the file twice (or even more) then continued to download the file with the same speeds for each ‘cut up’ file; you get a faster download. Also if all users have this ability, a torrent may survive longer, if seeders drop out the peers will have a piece of the complete file each t share together. Could bitcomet do this within the program instead of having to run bitcomet on multiple computers?
I know DAP (Download Accelerator Plus), a download manager is made on the same principle idea.
Some of what you mention is done by every bittorrent client, the rest that you mention is also done by bitcomet.
First of all, your performance when using torrents is limited by your ability to upload, so if you run bitcomet twice, then you’re reducing each computers ability to upload by half, so they will be less attrative to the better peers. You’re also compounding the problem of saturated upload bandwidth making your response time slower, this alone will kill your download performance.
You’d be far better to simply adjust your settings to match your connection speed.
Also, Bitcomet has http/ftp download management built in, so it can download http/ftp tasks using upto 20 connections for each file, however bittorrent doesn’t download files, it downloads pieces of files, so a large file could already be divided into thousands of pieces (or more). In otherwords, this is already built into the protocol so it doesn’t need to be added.
The only client that I’m aware of, which does this is uTorrent (it doesn’t mean that there aren’t others out there, I just don’t know about them).
That feature is called “Local Peer Discovery” and it basically detects if there are any other BitTorrent clients (LPD-enabled) on the local network (LAN).
If it detects any, it will use it as a local peers and download/upload towards it at massive speeds (the ones of your LAN) by establishing a local connection to the peer.
That doesn’t split files in 2 or 3 since BitTorrent clients DON’T download/trade files but pieces which are much smaller, so what you propose is redundant and doesn’t apply in BitTorrent.
Wiz, I don’t think that’s what local peer discovery is in utorrent. By default, utorrent won’t even allow a peer in your LAN to connect, you have to change the advanced option (bt.allow_same_ip) before a client on your LAN can connect.
I also don’t think this was his question. He wasn’t talking about downloading from a computer on the LAN, he was talking about getting slow speeds that use little of his bandwidth, so running the torrent on two computers.
computer 1=10% of bandwidth
computer 2=10% of bandwidth
so if they worked in concert, they both would get 20%, however computer 1 properly tuned would probably get 50-80% if their upload isn’t choked.
I believe he is under the same common (flawed) theory that if one task is slow, then run ten at the same time so you can get a good amount of download, instead of properly adjusting your bandwidth so you can become a good peer and download at fastest possible speed.
I’m not sure if LPD is disabled by default or not in uTorrent. I’m not sure what the option you mention does, either. Are you sure it’s about the public IP and not the local one?
LPD, does allow you to share the “burden” of download but probably it’s not designed with the user who has 2-3 computers on his own LAN running the same torrent. Rather it has in mind users on a larger LAN such as a whole building, dorm or campus or even a metro-LAN. In that case, if you find peers for the same torrent you can greatly benefit from the high speeds of the LAN instead of the Internet.
What exactly are the setup options to make this work I’m not sure, as I’m not extremely familiar with all features of uTorrent.
I asked once if the team would consider introducing this, but they seemed uninterested at the time so I dropped the whole question.
I know that this isn’t exactly what he asked about, but his post doesn’t make much sense either, since clients don’t work with files but with pieces.
There is no mechanism for two different instances of a bittorrent client to coordinate with each other. IOW, no client can say, “you download this part, while I download that part” – whatever those parts may be.
Because of that, you would get a lot of redundancy in a setup like that, with both clients downloading the same piece. One or the other of those pieces would be just wasted bandwidth.
This probably could be done with enough effort, but I see very little demand for it, really. Most people’s situations just wouldn’t benefit from it most of the time.
Thanks Wiz, I had never read that. I thought it worked more like PeX.
I’ve actually used the advanced option to allow same IP to (in effect) do the same thing. When I was testing Kluelos bug repoort for “creeping peers” (I really should edit that because it probably doesn’t translate offtopic), I downloaded the torrent with bitcomet, then started it with utorrent and as soon as I allowed same IP connection, my bitcomet began sending it speeds over 8000kB/s. It was less effort then transferring the files over the lan and rehashing the torrent, plus I wanted to give the torrent chance to gather peer lists.
so of LPD does the same thing, then it obviously cannot find a bitcomet peer.