Increase Max Torrent file supported

please increase the maximum torrent file limit , when i tried to download a 1 TB+ torrent , it showed an error indicating the torrent file is too large

Obviously your terminology is mixed up here. a torrent file is rarely larger then one megabyte, so I’m assuming that your trying to download over one terabyte of files in a single task, is this correct?

I’ve never tried to download more then 200gB of files in any one task before, in fact I’ve never seen a task exceeding 1TB. If there was, I don’t think bitcomet would object to downloading it though, can you provide an example of this torrent so our development team can examine it?

sorry for the late reply

here are the information:

Torrent File(the .torrent file): 5.26 MB (5,522,636 bytes)

Torrent contents: 972.7 GB

this is the error i get when i add the torrent file :Torrent file too large

screenshot: http://i1019.photobucket.com/albums/af314/mahadev_doom123/bitcomet1.png

I run a torrent tracker, and it uses one of the worlds most popular tracking software and it would NEVER allow a torrent file over 5mB to be uploaded, not even 2mB in fact.

The biggest torrent file I’ve ever seen is 1.6mB. The task size was about 600gB I believe, but that isn’t what makes the torrent so large. That task probably contains many thousands of files, and simply put, the author of that torrent was an idiot (don’t know any “kind” way to put it).

If you must put that many files in a single torrent, then you will need to archive them, encoding all those file names within the torrent is only putting way to much overhead into the torrent task and will make everyone unhappy, trackers and clients alike.

It’s also possible the torrent was made with a very poorly coded piece of software. I know it wasn’t made with bitcomet or utorrent, because neither of these would let a user make such a beast.

If you insist on downloading this task, then send me the torrent and I’ll try to dissect it and tell you what it was made with, then you can ask them what client will allow you to run such a torrent.

If you want a second opinion, here is a quote from Firon (utorrents administrator)

µTorrent won’t open torrents with more than 65535 pieces by design (because it’s retarded to have that much). With a 4MB piece size and 65535 pieces, you can do about 255GB (and the max piece size is 16MB so you can do about 1TB really…). You should tell the torrent maker to not be retarded and use a reasonable piece size. And you know, let the client do it automatically.

This was in response to utorrent being unable to open a 1.8mB torrent file, so you can imagine how absurd a 5mB torrent is.

ps. he has a good point, assuming the author let the client set the piece size, I assumed it was just a matter of to many files, but if they forced it to use a small piece size on a task that large, then the torrent would be huge.

I’d also consider if you want to trust the content of a torrent made by someone who knows so little about making them. Who knows what type of malware might be in it.

actually he is highly trustfully , and the torrent contains more than 10000 files i believe

the torrent file is : http://www.nyaa.eu/?page=download&tid=224684

the previous version of the torrent was 780 gb and the torrent file was somewhere around 4.4 mb and i could download it using bitcomet

My personal opinion is that the size of .torrent file currently supported by BitComet is reasonably high enough.

Anybody who has so much content to share should split it into smaller collections and seed them simultaneously.

I don’t know if there is a client out there which supports such big .torrent files.

This torrent seems to have been made with mktorrent and like most applications ported from Unix, this one probably comes with not so many “safeguards” in place as those programmed in Windows environment. Usually people working in Unix environments know better what they’re doing in front of a computer and I think that the author of the application didn’t put any constraints into this option, in order to offer as much liberty as possible to a user who wishes to make a torrent (and perhaps experiment some things) but not as an incentive to make such big .torrent files.

Your torrent uses a 4MB pieces size and has an insanely high number of over 240.000 pieces!

If the team chooses to increase the allowed torrent file size or not, for that you’ll have to wait for Ariel to forward your question to them and to receive an answer.

In the meantime, if you have any means, you should try to contact the author of the torrent, congratulate him first for uploading a torrent which can’t be downloaded in exactly any client and then perhaps ask him what’s his recommended application for downloading this “mammoth”.

If he made the piece size 16mB instead of 4, and put the 10,000 files in a dozen or so archives, that torrent would probably be less then 2mb, perhaps less then 1.

If you do find a client to run this file, I recommend you disable DHT, that would be a huge amount of data to pass around as overhead.

I also feel torrents should be kept as lean as possible, so allowing such an inefficient torrent to be created would be bad thing, but I agree with Wiz that Linux programs generally rely more on the user to know what is best, where windows programs tend to default to what is best for the swarm. Nothing against Linux, I use it myself and it’s a powerful operating system and it gives users more freedom to do things how they want to, not how the computer wants it done, but in this case, it allowed some very bad decisions to be made. Perhaps the uploader meant well and is reliable, but he really should re-author this torrent. (my opinion)

i see, thanks for helping me out and sorry for taking your time . But will there be any consideration in increasing the allowed torrent file size?

That answer would have to come from development. At very least I will try to find out the exact limits that bitcomet does allow and add the data to wiki.bitcomet.com (Wiz, would you mind checking if the info exists, and add any updates if we get new information).

The representative from our development team is “zerojinn”, she will reply if she gets a specific answer on this.

I’m inclined to believe this would be a bad idea. Seems to me that the overhead for such a torrent would be huge, compared to a torrent made with the same source files with larger piece size, and the files archived so there is less then 1000 (preferably much less).

I’ll also add a request of my own here. If we allow users to run torrents made like this, then that might be nice, being we are likely to be seeing more 1tb+ torrents in the future, but can we get some sort of popup tip advising users to put files in archives if the total file count on a torrent is extremely large?

We should also probably make a guide teaching users how to archive files to reduce this problem on extremely large tasks, and more important, the reasons why they should do so.

ok , thanks you

Nope, TUUS, I’ve never seen that info in the Wiki. And I don’t remember ever reading it on the forum.

Probably because this is such a rare and exotic error.

If the team will tell us, we’ll make sure to add it in some place in the Wiki.

However, TUUS, I’m afraid that the size of the .torrent file is due to high number of pieces of the torrent and their corresponding hashes into the .torrent file.

If you load the .torrent file into an editor (which is capable to load it, 'cause Notepad hangs forever) you will see that the text part comprising filenames and all the stuff before the piece hashes section is only 10% of the file.

Actually, out of curiosity I’ve copied the part before the hashes section into another empty file and saved it; it only had 529KB!

So, making it into a RAR, wouldn’t help much in this case. Perhaps making the piece size bigger would help reduce the number of pieces and thus file size, but anything above 4MB is highly inefficient in terms of pieces which may not pass hash-check.

I don’t really think we’ll see that many 1TB torrents, soon. I mean there aren’t a lot of things which can be organized into a logical collection that would occupy that much space. OTOH any idiot who will dump a whole HDD into a torrent and name it “My Movie Collection” or “My Crazy Stupid Music Collection That You Won’t Be Able to Listen Into a Lifetime” shouldn’t be given that much attention.

AFAIK there is a quite reticent stance in the BitTorrent scene towards very big piece sizes and very big .torrent files, and I think BitComet is more than welcoming towards .torrent files as it is at present time. I’m not sure if we should be the first to raise the bar in this case, as it may be regarded as an irresponsible gesture which encourages dumb users to create even more monstrosities of this kind.

Anyway, if anyone thinks different or can summon a good reason to have such big files, perhaps I’m wrong.