Using auto cache has bad influence in both situations. Maxed my speed within seconds and it stayed like that as shown at the speed graph. Memory usage around 122MB.Ĭompared to the TCP test this one was actually very good. Not quite stable and it took much longer to even max my speed. Straight line speed without any huge spikes or fluctating behaviour. Here are the test results with different cache settings and uTP/TCP options.Įven better than the first one in my opinion. With these assumptions, it's the only scenario where auto would cause the spikes. With these 2 datapoints we can get closer exactly what the problem is with auto, because libtorrent uses the amount of total system memory to determine the value of auto.īecause 5 GiB > 4 GiB and 5 GiB/40 = 128 MiB, and given that with 128 MiB, performance is good for we can deduce that if the spikes have to do with lack of cache, machine has to have less than 5 GiB RAM. No need to go until the end, you'll reach a small interval of possible values in very short time. For example, if 128 MiB is good, try with 64 MiB. I recommend using a binary search procedure to make the process faster. The minimum value you can manually set the cache to that does not result in the spikey behaviour (does not need to an exact value, can be a ballpark within a few dozen MiB or so.
The spikes on the left are auto, the lull in the middle the transition period and to the right with the 128MB post: Everything stopped for a little while, and then it bumped back up to a steady 15Mbps or so. The below picture shows what happened when I went from auto back to a 128MB cache. So again, as a test, I set it to auto allocation and let it run for a while. This time it kept the 128MB allocation (maybe because I'd set it manually rather than the default in 4.2.1?), and things were smooth. Then it occurred to me that in 4.2.2, the cache allocation had been set to auto, so I've gone back to 4.2.2 again. In my 4.2.1 install, I noticed spikes after a while (not as bad as in 4.2.2), and based on one of the other bug reports here, decided to up the memory allocation for the cache from 64MB to 128MB. Just to tack on another data point which makes me think it has something to do with the auto allocation for the disk cache. In this case it was 32GB in size as shown. Not once but it keeps doing it till the download is finished.
See the screenshot, enough seeders to max out but still seeing the speedgraph from last 5 minutes (if its working right) you can see the speeds go up and down. I only changed my own settings within speed and connections tabs. Thats what I have found for myself.Īdvanced settings is all default. But as I said it does happen with large torrents with big piece sizes in general. My system is doing nothing else on the background. Downloading to HDD and SSD doesn't solve it by the way. For some reason it goes up and down which shouldn't be happening. I want it to stay at stable speeds when there is more seeders than leechers available. Especially with big piece sized torrents from my experience. While this doesn't happen with every torrent with large torrent it seems to happen more often. My max downloadspeed is around 12MiB/s at the moment. Also I see that my speed go up and down (between around 9.0MiB/s and 5.0MiB/s and sometimes jumps to my max for few seconds) so it confirms the speed is going up and down for some reason.
0 kommentar(er)
