I'm a little confused with disk caching in my set up, I'm assumng it caches the data in the drive where the torrent is stored? Or am I wrong and it caches it on the OS drive where the client is running?Downloaded blocks are cached in memory, and written to disk every so often so as to minimise the number of disk writes/reads. You can tune when and how often blocks are written out to disk. Set it too high/frequent and you have heavier disk IO; set it too low and you have high memory usage (for a fast connection, that is).
| @flynn | : Hmm, Basically what Kureshii said. and it has nothing to do with the OS/Directory drive i think, but rather where the torrent files are, which would be on either depending on where you saved it. anyway, regarding the IO r/w & caching settings skyrocketing CPU usage I think it was because of the large number of blocks in the torrent, and there were huge gaps between the pieces but i'm not really sure how that causes utorrent to do extra work on seeding, in fact, the number of pieces may have nothing to do with it at all, so don't take my word for it on this. to explain further why i think this is the problem: the torrent itself was around a few hundred Gigabytes, and has thousands of files. Going about my usual torrenting habits nothing happened for a few weeks, but as i downloaded more and more files (but not all of the files in it) utorrent would randomly consume an insane amount of CPU while seeding. So, I tweaked around with the caching and it solved the issue. but as i've said, i forgot the exact settings. and i don't really get why it worked myself. I'll try to add the torrent again sometime with uT 1.8.5 and see if it still happens with the default cache settings. |