Have a i5 3770k with 8 Gb, win 7, qbit 4.1.2 (64 bit) and my connection is 80/8 Mb.
Seeding around 2000 torrents, which optimal cache settings are recommended for my setup ?
Disk Cache= MB ?
Disk Cache expiry interval= ?
Enable OS cache= ?
Guided Read Cache= ?
Send buffer watermark= ?
Send low buffer watermark= ?
Send buffer watermark factor= ?
Thanks!!!
cache recommended settings for 4.1.2
-
Switeck
Re: cache recommended settings for 4.1.2
From very slow HDDs, even a huge cache will only help a tiny bit because multiple peers won't be downloading the same pieces from the cache.
Seeding from very fast SSDs ...the cache is almost unnecessary.
Seeding from multiple HDDs or SSDs at once should reduce the load on each and a large cache won't be needed.
With only 8 GB ram and likely used by other apps a good bit of the time, I would recommend a cache of only 200-500 MB size.
If the computer is mostly dedicated to running qBitTorrent and you don't mind limited ram availability, set it as high as 1000 MB.
Disk Cache expiry interval max is 600 seconds last I looked, and that's what I use.
You'll need to test Enable OS cache to determine if it "eats" much/most/all your ram and prevents it being used for other things.
If the OS cache is disabled, you may want to bump up qBT's cache to 1000 MB or even 4096 MB if the computer isn't used for much else. The values can be lowered and free ram almost instantly if more free ram is needed for other things.
Guided Read Cache supposedly lets qBT grab parts of the torrent not requested yet on the assumption that those parts will be what a peer requests next. Also might cause qBT to remove from cache already-used parts quicker. qBT shouldn't be uploading the same piece over-and-over again back-to-back, so a "smart"/guided cache logic should be better than a simple one that just caches whole pieces.
Send Upload Piece Suggestions option sadly should be left disabled due to a bug I encountered in high-speed upload tests by qBT -- BUT this may have been fixed since I last checked around v4.0.0! It's supposed to hand out a list of "HAVE FAST" pieces that peers can download faster than others because they're rare pieces, but it caused my upload speed to run at about 10 MB/sec instead of 100+ MB/sec (so less than 1/10th as fast) as when it's not enabled. Despite the bug, it might work well enough being enabled on internet connections with less than 100 mbit/sec upload speed devoted to qBT.
I wouldn't mess with the buffer watermark settings -- those only start to matter when HDDs cannot keep up, like at 1 gbit/sec (~120 MB/sec) DL speeds.
Seeding from very fast SSDs ...the cache is almost unnecessary.
Seeding from multiple HDDs or SSDs at once should reduce the load on each and a large cache won't be needed.
With only 8 GB ram and likely used by other apps a good bit of the time, I would recommend a cache of only 200-500 MB size.
If the computer is mostly dedicated to running qBitTorrent and you don't mind limited ram availability, set it as high as 1000 MB.
Disk Cache expiry interval max is 600 seconds last I looked, and that's what I use.
You'll need to test Enable OS cache to determine if it "eats" much/most/all your ram and prevents it being used for other things.
If the OS cache is disabled, you may want to bump up qBT's cache to 1000 MB or even 4096 MB if the computer isn't used for much else. The values can be lowered and free ram almost instantly if more free ram is needed for other things.
Guided Read Cache supposedly lets qBT grab parts of the torrent not requested yet on the assumption that those parts will be what a peer requests next. Also might cause qBT to remove from cache already-used parts quicker. qBT shouldn't be uploading the same piece over-and-over again back-to-back, so a "smart"/guided cache logic should be better than a simple one that just caches whole pieces.
Send Upload Piece Suggestions option sadly should be left disabled due to a bug I encountered in high-speed upload tests by qBT -- BUT this may have been fixed since I last checked around v4.0.0! It's supposed to hand out a list of "HAVE FAST" pieces that peers can download faster than others because they're rare pieces, but it caused my upload speed to run at about 10 MB/sec instead of 100+ MB/sec (so less than 1/10th as fast) as when it's not enabled. Despite the bug, it might work well enough being enabled on internet connections with less than 100 mbit/sec upload speed devoted to qBT.
I wouldn't mess with the buffer watermark settings -- those only start to matter when HDDs cannot keep up, like at 1 gbit/sec (~120 MB/sec) DL speeds.