Vuze is EXTREMELY slow after updating to 5.7.0.0

[Onbekend]

Hello Everyone!

Vuze is now extremely slow downloading files since I updated to version 5.7.0.0 (Interface is working fine). I did not change anything else. What is going on here? Please help!

Thanks!

[GaryE]

It is likely it is just that the torrents you choose to download have slow swarms.

That is the usual reason for that complaint.

How many torrent have you downloaded since you upgraded?

[trek7000]

Hello Everyone!

Vuze is now extremely slow downloading files since I updated to version 5.7.0.0 (Interface is working fine). I did not change anything else. What is going on here? Please help!

Thanks!


 

I'm having the exact same problem. The speed limits are set at 500KB/s down and 50 up, yet I'm only running 25 down and 5 up. After ruling out issues with AirVPN, the Vuze update seems to be the only culprit. I'm downloading the Vuze 5.7.0.1 beta, but... it's downloading very slowly!

[GaryE]

For what it is worth I finally updated to 5.7 a few days ago . . . I have noticed no decrease in upload or download speed since then.

[trek7000]

Well, I upgraded to the 5.7.0.1 beta and it didn't make a difference. So I downgraded to the 5.6.2.0 and it was blazing - for a few hours. Now I'm back to where it was before. I'm stumped.

It doesn't seem to be AirVPN causing the slowdown, so I thought maybe it was slow swarms as you mentioned. But the actual Vuze update ZIP downloaded at 3.7KB/s, so I'm not sure.


EDIT: I swear on my (still living) mother's grave that as soon as I typed this reply, the speed went back up to max. Vuze is watching me...

[Havokdan]

Its Big Brother.

[panran]

Hello Everyone!

Vuze is now extremely slow downloading files since I updated to version 5.7.0.0 (Interface is working fine). I did not change anything else. What is going on here? Please help!

Thanks!

 

not hijacking your thread,but same thing is happening to me.And I can't change my listening ports,they keep going back to 8374.Anyone have this problem?

[fields]

Its Big Brother.

 

They all are younger brothers, not big, big is you one, me.

[trek7000]

Hello Everyone!

Vuze is now extremely slow downloading files since I updated to version 5.7.0.0 (Interface is working fine). I did not change anything else. What is going on here? Please help!

Thanks!


 

not hijacking your thread,but same thing is happening to me.And I can't change my listening ports,they keep going back to 8374.Anyone have this problem?

 

I haven't messed with any port settings, so not sure on this one. My speed is still all over the board - blazing one minute, turtle slow the next. After the current round of downloads finishes I'm going to investigate a bit more, hoping it's just a single bad swarm causing the issue.

[GaryE]

I have been living with 5.7 for about 2 weeks now . . . I have had a few issues (particularly today but I think that was just a weird random thing my computer actually rebooted twice but I think it was a browser problem) but nothing too out of the ordinary.

I can tell you that if anything the memory and CPU usage seem to be down and if anything the speed uploading is faster.  I really do not do that much downloading (and much of what I do download is done automatically so I do not always see the torrent as it is actually downloading) but from what I have seen if anything it is slightly faster.

I guess it is possible that some of you are getting traffic shaped and that traffic shaping just started to take place on or about the time you upgraded to the new version of Vuze . . . but that seems extremely far fetched.

I do not doubt that you all are having problems . . . but as I said early on in this thread . . . the usual suspect for slow download speeds is just a slow swarm.  If you have downloaded say the same TV show from some tracker/site every week (or every day or whatever) say 15 or 20 times before you updated Vuze and you have downloaded that same TV show say 4 or 6 times since . . . you then might be able to see a pattern.  But if you all are just basing this on an odd torrent or 5 or 8 from different sites (or even the same site if that site is a public site) it is hardly a definitive sample size.

In the interest of full disclosure since 25NOV15 [when I upgraded] I have downloaded 23 torrents 11 of which are a TV series I have downloaded 6 times a week since 01JAN15.  I get this TV show from a private closed invite (at least now) site and the same user uploads the show every time.  That is as close to as a controlled test as you are going to get.  That TV show is downloaded automatically so I am not always at my computer when it downloads but on the roughly 4 or 6 times I have been at my computer when it was downloading [since the upgrade] I have noticed that the speed is the same as usual or maybe a bit faster.  The other 12 torrents are a mixed bag from different sites and different uploaders but again if anything they seem a touch faster.

[trek7000]

Thanks for your response, Gary. I currently have 17 random torrents downloading and am seeding 151. My first suspicion was that Comcast was throttling VPN traffic, but I get 12MB/s down and 5 up if I shut Vuze down and test the VPN speed. I've tried everything I can think of, even downgraded to 5.6.2.0, upgraded through the various betas, paused all downloads, paused all uploads, reset settings to default, etc.

My thinking is that either the 5.7 update or a bad torrent pooched something, so my plan is to wait for the current torrents to (slowly) finish and then start from scratch.

[GaryE]

You are welcome!!

Comcast is notorious for all kinds of madness.  The issue you are describing with yo-yo speeds is a classic sign of traffic shaping.  The supposedly do not do traffic shaping anymore . . . but there are just too many reports of them doing exactly that (shaping traffic).  The problem is that many of the local Comcast offices were bought by Comcast and others have always been Comcast.  There is just no concrete data on this but it has always been my assertion that the local affiliates who were bought out by Comcast kind of do their own thing and do not necessarily adhere to "corporate" policy.  Or maybe it the opposite . . . that the affiliates who were originally owned by other companies do not do the traffic shaping but Comcast owned from day 1 affiliates still do traffic shape.  Again there is just no data on this and I have never been able to get enough data to say what is happening.  But I do not trust Comcast any further than I can throw them.  Comcast does what is best for Comcast and they do not really care about anything else.  It is very possible you are getting shaped.

first check here and locate your ISP.

then read this for suggestions on how to avoid your ISP's efforts (if necessary)

The words here and this are links ;-)

If those links do not help try running a glasnost test:

http://broadband.mpi-sws.org/transparency/bttest.php

That should tell you for sure what is going on.


note:  That is a standard traffic shaping text that I keep on my desktop.  Since you say you are running a VPN you can scratch all of the stuff about changing ports . . . if your VPN is set up correctly changing your torrent ports is not going to do anything.

Again yo-yo speed is classic traffic shaping and Comcast has always been one of the most aggressive traffic shapers there is.  It would not surprise me to learn that they are shaping all of your high volume traffic simply because you are using a VPN.

I really do not think this is an endemic problem with the current version of Vuze.  Either that or I have changed some settings in a special way which somehow obviates the issue.

Good luck and let us know what you discover.

[trek7000]

Whelp, I figured it out.

Glasnost over straight Comcast pipe and over the VPN showed no traffic shaping

Running AirVPN, Vuze not running - Speedtest.net result: 9.4Mb/s down, 5.2 up

Running AirVPN, WITH Vuze running - Sppedtest.net result: 0.45 down, 0.84 up

Vuze has consistently been running 30KB/s down, 5KB/s up


I looked in add/remove programs, and it turns out AirVPN updated the same day I upgraded to 5.7, and apparently it reinstalled the TAP adapter on a different eth port.

Vuze has always been bound to eth11 - I changed the binding to eth16 and it is flying like it's supposed to.

Thanks again for all your help and suggestions!

[GaryE]

Well it is refreshing to hear that Comcast was not doing anything nasty!

I am glad my questions helped you indirectly find the cause of the problem!  You are welcome!

[mjjh]

 

I have the same problem, but only with the 5.7
I have the same VPN running on my laptop, and the 4.8 client.
5.7 slow.  4.8 fast!!!

[fields]

Whelp, I figured it out.

Glasnost over straight Comcast pipe and over the VPN showed no traffic shaping

Running AirVPN, Vuze not running - Speedtest.net result: 9.4Mb/s down, 5.2 up

Running AirVPN, WITH Vuze running - Sppedtest.net result: 0.45 down, 0.84 up

Vuze has consistently been running 30KB/s down, 5KB/s up


I looked in add/remove programs, and it turns out AirVPN updated the same day I upgraded to 5.7, and apparently it reinstalled the TAP adapter on a different eth port.

Vuze has always been bound to eth11 - I changed the binding to eth16 and it is flying like it's supposed to.

Thanks again for all your help and suggestions!

 

I've figured out that case just by don't specify VPN's bindings in Vuze, any binding at all, switching it off, so, I absolutely don't care about that and it successfully works.

Because there're in the Viscosity VPN client by TorGuard VPN-service used by me now already option of transmit all traffic through VPN tunnel, so, not much need bind VPN interfaces in Vuze. Also the same available for L2TP connections in Viscosity, apart from OpenVPNed connections.

I am only slightly thinking about staying with TorGuard, little problem with port forwarding (success port forwarding somehow only with a few servers-IPs, affraid telling only with one LeaseWeb-Frankfurt, for example, others 3 IPs-servers activated in the Port Management in Client Area won't openning ports). Maybe there're something is going on with a router or something else like IT-criminals-attackers. By the way router's TP-Link MR3420 v.2.2 firmware is not-stock latest trunk OpenWRT Barrier Breaker, which as I saying non-problematic working only somehow with LeaseWeb's Frankfurt server-IP in TorGuard.

Planned try bringing back original stock firmware, if that can helps, will see.