Is this normal behaviour or is some wrong with my setup? Or is utorrent itself under attack somehow? Link to comment Share on other sites More sharing options Posted December 14, Switeck Posted December 14, Have you tried Ultima's Troubleshooting Guide? Archived This topic is now archived and is closed to further replies.
Go to topic listing. Sign In Sign Up. This will give you a more stable download platform to work with. Depending on where your router is located in the home, it can pick up interference as it travels OTA. This happens when a person downloads a torrent from another person, and suddenly, the seeder leaves. The person cannot get the entire file, but more people then start downloading from him or her.
This results in an incomplete torrent with several people waiting for the original person to come back. You can find another torrent, wait for the person with the whole torrent to show up, contact the copyright owner of the purchased product to get it via other means if it is a commercial product , or add trackers as shown in this tutorial. There are no peers showing for the file and only 4 trackers which ain't working. What should I do to increase the speed? By Phontsy , May 6, in Speed Problems.
That one was in San Marcos and this next one is in Dallas where the location for the setup guide is. Start new topic. Recommended Posts. Phontsy Posted May 6, Posted May 6, It maxed at around 8. Didn't go much higher than that. Great results again. RAM usage around MB and as seen on the speedgraph the speed was quite stable at some point reaching my max. Nemo-qB Thanks, it sounds increasingly more likely that there could be some problem with auto.
In an ideal world, the qbt graph would be able to plot all metrics not just the downloaded and uploaded bytes. Anyway, I would be interested in knowing if this could be an issue in uTP. TCP disabled, only uTP:. Even better than the first one in my opinion. Straight line speed without any huge spikes or fluctating behaviour.
Memory usage around MB. Mixed feelings. Not quite stable and it took much longer to even max my speed. Compared to the TCP test this one was actually very good. Maxed my speed within seconds and it stayed like that as shown at the speed graph. Auto cache, only uTP:. Auto cache, only TCP:. Using auto cache has bad influence in both situations. This could explain the speed problems that some are experiencing. The memory usage of both tests is the lowest of all comparisons. I personally don't really care that much about memory usage as long the performance is good.
I got 16GB so its more than enough. Thats why I keep my cache setting at MB for now to see how it goes with different torrents. If im right uTorrent is set at MB too as default. FranciscoPombal arvidn sledgehammer Also, if it returns 0, you might want to change the default cache value to something higher than 16 MIB, say 32 or even 64 MiB. But this still won't be enough for many cases, and it's not a real solution to have the fallback value be very high, so you should probably issue an alert.
I was truncating the total physical RAM to a signed 32 bit int. So, 16 GiB would become 0. How does this look? Also, if possible, set a breakpoint at the relevant location in the libtorrent source and observe the value that is returned from the function with and without the patch. Nice find, hopefully it will be fixed as I think that the most of the speed problems is caused by this behaviour.
At the moment im using MB cache without issues for now v4. I hear that my system is much more quieter and performs excellent. I too also went from auto to MB for the cache and instantly, the random bottoming out.
You can notice clearly when I hit "apply" on the setting. EDIT: File below: qbittorrent 4. Nemo-qB Disco-Chef mcmuttons can you please test this build?
Set the disk cache to auto and see if the problem is fixed i. I'll install it tonight and see.
0コメント