I try to give BC lots of DRAM for cache, and it doesn’t seem to take all that much of what it is offered and the disk is getting hit too much and is probably the limiting factor on my total transfer rate. This example is basically just upload (IP is fully routable - I’ve xxx’d for privacy):
Overall Infos: Torrents: 54 | Peers: 66 | Sockets: 574 (HTTP: 1)
TCP Connections: Established: 65 | Half-Open: 1 | Waiting: 0
LAN IP: xxx.xxx.30.253 / WAN IP: xxx.xxx.30.253
Overall Download Rate: 5 KB/s Connection Limits: 85 - 85 per task
Overall Upload Rate: 4645 KB/s Upload slots: 100 - 100
Disk Cache Size: 554.50 MB (Min: 20 MB, Max: 1200 MB)
Free Phys Mem: 784.81 MB (Min: 100 MB)
Disk Read Statistics: Request: 390119 (freq: 268.9/s), Actual Disk Read: 25747 (freq: 17.7/s), Hit Ratio: 93.4%
Disk Write Statistics: Request: 668 (freq: 0.0/s), Actual Disk Write: 47 (freq: 0.0/s), Hit Ratio: 92.9%
Total Downloaded: 98.51 GB
Total Uploaded: 1,035.80 GB
In this case there is still over 1/2G of DRAM it is welcome to take and it won’t use it, but the disk is getting 17.7 physical reads. Certainly caching has made that better than the 268.9/s it never could have kept up with, but what can I change to use even more cache?
