![]() Side Notes: Have been using the migration to do several tests, and it seems that part of the slowness in my main PC setup with NAS as local drive is caused by some kind of bottleneck caused by pairing qBittorrent with a NAS, when checking data if i monitor the NIC graph, it uses almost no bandwidth(less than a megabit/s, usually around 500kbps or less), but when "re-checking" files it uses as much as 1000mbps (around 100-120MiB/s) from time to time. Storage: Locally linked "Share" form Host:"/mnt/user/Torrents/" to Docker:"/downloads/torrents/"ĭata: Same 4000+ torrents (i just finished migrating everything today) Local media server running unRaid (this is "the NAS"): Storage: RJ45 direct connection to NAS over 2,5Gb NIC, unit mounted as "T:" drive. In case it helps, i will put my 2 systems that i'm running qBittorrent below: I have a strong suspicion that qBittorrent v4.6.X+ have some kind of problem that prevents it from reading parts of the ".fastresume" data and it regenerates it on "every-damn-startup", installing ANY previous version fixes the problem INSTANTLY, "check resume data" on v4.5.5 is instantaneous, it "just happens". ![]() with 4000+ torrents(14TiB+) nowadays it takes me HOURS to finish the check of the resume data of all my torrents.(local network NAS with 2.5Gb/s NIC and 200MiB/s R/W speed). ![]() ![]() This seems as a common and really under-reported problem that was driving me crazy since the release of 4.6.0 and that i hoped after several updates it would be fixed, after every patch i kept seeing the same problem every time. ![]()
0 Comments
Leave a Reply. |