When a file has been stopped, or if the program times out, or something like that, before it begins downloading again, it goes through a Checked x% process which I have found is taking a very long time for a big batch. I have read some threads related to this, but they are locked. I did not answers in them. This isnt about improving the actual speed of downloading, but rather, actually getting to that downloading phase by completing the Checking. I think this is an offline process that does not require Seeder interaction. Something about matching up the .torrent cues with the actual files being built up from the Pieces in the batch. I am wondering what the limiting factors would be in Checking and what changes could be made to lift them and speed up the checking. Ive noticed that Im 5% done in 6 hours, and Im thinking it shouldnt take 5 days to do this. This is something I downloaded 23 of 28 gigs of in a single day. Why would it take longer to check a file than to download or build it?