gavana
Advanced Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
It is NOT what resources you think you can spare, but you should only tie up resources that can be actually required.
BitTorrent clients handle data in 16kiB blocks and it is the number of BLOCKS that are active at any one time that require caching NOT the entire payload or complete 'pieces'. When your client is downloading and has a much larger cache than required it writes more data to the drive every time, which takes longer than writing small amounts of data more often. The hard drives do not need to 'spin up' and 'spin down' as often which reduces the write time and lets the drive interface handle the write queue more efficiently, it also reduces the wear and tear on the drive, because it is the continual stop - start processes than more damage than leaving them running at full speed all the time does.
If you have ten or twelve VERY active jobs a cache of 256kiB - 384kiB is more than enough, that gives space for 20 - 25 blocks at any one time, for the average 'casual' user 128kiB is more than ample.
Don't be fooled with the "more is better" dumb arse "Speed up BitTorrent" videos on YouTube, following their examples is more likely to screw up your data rates.
'Enough' is better. Same with trying to get more "Free memory" as displayed by Windows Task Manager, in that "Free Memory" is wasted memory, because it means that applications cannot use it for some reason, 'Free' doesn't mean 'available', 'free' means 'not going to be used', |
Всего записей: 1524 | Зарегистр. 14-03-2003 | Отправлено: 22:56 14-09-2019 | Исправлено: gavana, 23:07 14-09-2019 |
|
