I can confirm a spike in the verification process. As I already told Roger Kapsi, it would probably reduce a huge bottleneck if the verification of chunks while downloading would be verified in memory instead of writing to the disk, then verifying it. Verifying it in memory cuts the read/write process in half since you download it, verify it in memory then write it to disk instead of downloading it, writing it to disk, then verifying it. Make sense? This could also potentially speed up the downloading process as a whole. I just know that its killing my disk with amount of read/writes its doing.
Or maybe a hyrbrid combination if the user doesn't have enough RAM? |