Can't decide whether to use QoS or continue capping Azureus

Discussion in 'Tomato Firmware' started by Sunspark, Jun 6, 2007.

  1. Sunspark

    Sunspark LI Guru Member

    Wondered if y'all have opinions on this..

    For some time now when it was just my connection and not shared, I used to simply just cap Azureus u/l at 15-20 k/s below my max.

    QoS is something new, and I have two choices here. To leave it capped at 90% of max for everything, and uncap Azureus fully. The idea behind 90% is that some places are slow and you don't want a backing up.. or I could just go to 100% of my max and hope for the best and have 1024-65535 as low priority.

    Or I could just run Az manually with a cap.. and that way nothing else gets throttled at 90% or whatever.

    Any thoughts?
  2. venk25

    venk25 Network Guru Member

    Before I throw in my 2c, Tomato's QoS is pretty good that if you just enable it, things will work good for most normal operations, including P2P. If you want specific priority for particular traffic (high priority for VoIP, for instance), you might have to make some minor changes.

    If you are now going to be sharing your connection (with someone else), I'd suggest QoS. You may be well behaved with your Azureus or anything else, but can you be sure about the other person ?

    Just an information - QoS means more work for the router. Not that the router can't handle it (assuming you are not going beyond your router's normal capability), its just more work for it. If/when you enable QoS, its always recommended to do 90% of your max upload speed, so that real-time traffic (read VoIP) will not be effected.

    FYI, some P2P users try to cheat by using ports < 1024. So, if the intention behind making 1024-65535 low priority is (also) to catch P2P traffic, you might be in for a surprise. However, Tomato's QoS is good that even such unscrupulous traffic will be put into low priority if the traffic is 512K+. So, you are protected there too ! If you want to give 100%, sure you could do that and make low priority not go till 100% of max bandwidth (like how the lowest is capped at 95%)

    Any lowest priority traffic, by default, is capped at 95% of the speed you put in "Max Bandwidth". If you P2P into lowest, you're already capping it.
  3. larsrya8

    larsrya8 LI Guru Member

    Bind Azureus to one local port; make a QOS rule for that port. Done.
  4. Sunspark

    Sunspark LI Guru Member

    Hmm interesting comments..

    Some info.. I am sharing the connection yes, but I am the only one who is going to run the P2P. <b>My intention is that the other machine continues to have a snappy web browsing experience..</b> so the outgoing is taken care of.. but I am noticing the incoming download is slowing down the web browsing because it's maxing out.. I am wondering if really what should be done is to have Azureus throttle the maximum download speed also so there is bandwidth available for 'other stuff'.. unless that is the same as QoS but for incoming bandwidth.

    I cannot 'bind' Azureus to 1 port, because it does open a bunch of other TCP ports in addition to the single port I set, for outgoing.. tho they all get defaulted currently to 'lowest'.

    I was just reviewing the rules, and I see if someone is <1024 it would be 'low' priority as the default which isn't all that different from the class below or above in terms of min & max #s.
  5. digitalgeek

    digitalgeek Network Guru Member

    The problem with this is because you will never be able to use this bandwidth P2P is the only traffic...

    With QOS, I only cap my Upload with utorrent. This way I am guaranteed that every computer will have it's equal share of upstream. QOS will evenly distribute you inbound as well so that your P2P will not take over...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice