Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Upload speed significantly decreases upon torrent completion.
#1
Hi All, Does anyone else experience a significant drop in upload speed when a torrent is finished downloading? While my torrents are downloading I have great upload speeds (2 - 4 MB/s) but as soon as the torrent is finished downloading, it drops down to 10 -​ 30kB/s. All the peer connections remain intact, but the upload speed just drops. This happen with all torrents, regardless of file type or size.

Anyone have any thoughts?

Thanks
  • MacOS X 10.12.2
  • Java 1.6.0_65 (64 bit)
     Apple Inc.
    /Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
    SWT v4528, cocoa
    Mac OS X v10.12.2, x86_64
    V5.7.4.0/4 az3
  • Verizon Fios
  • Do the Health status on your torrents have Green smilies? YES
Reply
#2
I assume you don't have an alternative upload max-speed-when-seeding set? If not, does it eventually recover?

By the way, is there any reason you haven't updated to Vuze 5.7.5? As part of that process it would update your Java from the very old Apple 1.6 version to a recent 1.8 one? You should have been getting prompts to update - is that process failing? Thanks!
Reply
#3
(03-16-2017, 07:56 AM)'parg' Wrote: I assume you don't have an alternative upload max-speed-when-seeding set? If not, does it eventually recover?

By the way, is there any reason you haven't updated to Vuze 5.7.5? As part of that process it would update your Java from the very old Apple 1.6 version to a recent 1.8 one? You should have been getting prompts to update - is that process failing? Thanks!

 

I do not have a max speed set when seeding, hadnt thought of that though, good call. I do see a slight recovery after a a day or so, but even then it will typically max out at 200-300 kB/s. The same torrents were getting 2-4 MB/s upload speeds during d/l. 

I havent updated my client because some of my trackers don't allow new versions right away. Crap rule, but what can I do.
Reply
#4
OK, hopefully your trackers will see the light sometime soon!

We're trying to get as many users up to Java 1.8 as the UI library we use (SWT) has switched to only supporting Java 1.8+ for new releases, so at some point there will be a fix in SWT that we need to distribute and older Java users will be stuck.

There are a few other seeding-specific settings that you might want to check, just in case, under Tools->Options->Transfer.

When a download completes there is a time while it rechecks the data (few minutes depending on file sizes) - this might interfere with seeding during that time, but it certainly wouldn't be that big an impact or sustained for long.

In case it is your ISP poking about you could try enabling the 'mask download completion' flag under the Transfer settings. This has other consequences but at least allows you to test this possibility.
Reply
#5
Ok, I tried enabling the 'mask download completion' flag as suggested and it made an immediate difference on restart of Vuze. But it didn’t last very long, maybe an hour and it was back to the same issue.  

However I tried something else that seems to have made a sustained difference. I had 7 torrents going and I waited until one torrent finished and went to seed. When it went to seed it had an u/l rate of 1.8 MB/s, within 30 seconds of going to seed the u/l rate dropped to 8 kB/s while maintaining the peer count. I made a point to have only the 7 torrents active globally so as to keep track of things. The remaining torrents had peer activity averaging about 25 connected with no u/l activity worth mentioning (due lack of demand).  

When I paused these six downloading torrents, the torrent that was seeding jumped up to 2 MB/s within a minute and has stayed that way. I waited a while and started the 6 downloading torrents again to see what would happen and the u/l speed on the seeding torrent remained high, it even seemed to experience a sustained increase. 

So now I will monitor and see if anything changes. Any thought on why this would play out like this? 

As an aside, am I better off leaving the ‘mask download completion’ flag enabled? What are the other consequences that you mentioned?
Reply
#6
The 'mask' option pretends that you don't have a random piece of the download to the rest of the swarm (i.e. they will still see you as 99.whatever percent complete due to the missing piece). So they will assume that you need that piece and make connections to you in order to send you that piece - wasting their+your bandwidth for as long as you run the download. Also it obviously reduces the overall availability of the download. The intention behind it is to interfere with ISPs that block/throttle seeding connections.
Reply
#7
I have the same problem.

VUZE does not upload well for completed torrent seeds.

I want to upload a lot, but I can not.
Reply
#8
This has been happening for years for me...

Upload speed always to the maximum limit... Until I download some torrent. Then it drops for a few hours after the torrent is completed. The more torrents, the more the general upload speed (not only for a particular torrent) decreases.

I don't have a clue why this happens.
Reply
#9
Options > Transfer = untick "Increase download speeds by biasing upload capacity towards incomplete downloads"

OR

increase the amount "KB/s minimum reserved for complete downloads"   AND  untick "attempt to apply bias when there is no effective global upload limit"
Reply
#10
I was having the same problem and I fixed it but I'm not positive I understand exactly why. I changed: 
Queue > Max simultaneous downloads to 3, 
Queue > Max active torrents to 6
Queue > Min simultaneous downloads to 1
Transfer > Max upload slots per torrent default to 15
Transfer > Max connections per torrent default to 100
Transfer > Alternate default when seeding to 55
Transfer > Max connections globally to 360

With no active downloads, I'm now getting uploads of 500-1,000 kB/s (with a ceiling of 1,150 kB/s). I'm not sure what aspect of these changes made the difference, but it's working for me now. With my old settings, I was getting 10-100 kB/s max upload (with the same 1,150 kB/s ceiling) whenever I wasn't actively downloading. Hope this helps.
Reply
#11
I think I've realized why this happens.

It's just because when one downloads some torrents with no peers to upload data to, Vuze keeps focusing all the resources on these new, high-ranked torrents, trying to seed them, as usual.

But as the torrents have no available peers, the upload speed remains 0 B/s for some time, until the priority changes.

Hope this helped improve Vuze on future releases.

Best regards.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Upload Queued ? TheBard 6 6,255 12-19-2017, 12:41 AM
Last Post: ekstasee
  [RFE] Allow tracker updates to torrent multiple times from magnet: & .torrent sources detelosk 0 1,264 05-26-2017, 10:07 AM
Last Post: detelosk



Users browsing this thread: 1 Guest(s)