aMule Forum
English => Feature requests => Topic started by: K-Marx on November 24, 2006, 08:01:10 PM
-
Hi,
I'd like that amule will be able to set an automatic and dinamic upload limit (USS like emule)
Thanks
bye
-
Hi K-Marx!
There's already a comparable function called UBT (Upload bandwidth throttler) added in 2.1.0
-
Thank you very much wuischke,
I have just the 2.1.0 but I don't find that function! Maybe you can help me, where can I find UBT and how can I set it?
thanks
K-Marx
-
It's enabled by default. To test it: Upload a file e.g. via FTP and watch aMule's Upload speed. It will reduce whilst the ftp upload will get more bandwidth.
Regards
-
For UBT work, i put limit download on "0" ?
-
No, it is always enabled. But it will not react super-fast, so please set an upload limit of about 75-85% of your upload capacity. (i.e. when you surf the web you use only little traffic for a very short time, so that UBT won't throttle the traffic for every page you visit. But you'll notice a slowdown while surfing and having aMule saturating your connection. But when you down/upload a large file via FTP UBT will recognize this and throttle the upload speed.)
-
Don't alone ftp, right? But http or pop3 also work ubt.
What is the logical of ubt? Watch line ping?
thanks
-
I don't like USS idea (because of the pinging and root access..ect)
but i would love to see the SUC implement (a proper dynamic upload setter) which is always active unlike UBT
info:
http://wiki.emule-web.de/index.php/SUC
-
Amule need a configurable UBT
See this example (Change in case 2 windows for linux):
http://forum.amule.org/index.php?topic=14216.0
-
nowadays people really need something like this because many isps are capping upload bandwidth at a certain usage, so for example if i leave my amule on 24/7 at setting 40, 5 hours in the day (random 5hours) the upload drops to 10kb and amule uploads slots are dropped and ping times are high. we need some sort of dynamic analysis of the users upload so the whole network gets more stable.
-
The more important features in amule should be:
1-fix crashes and other bugs
2- protocol ofuscation
3- best UBT, examples SUC or USS (users upload more) Example I always upload 20KB/s with USS about 25KB/s or more.
-
The more important features in amule should be:
1-fix crashes and other bugs
2- protocol ofuscation
3- best UBT, examples SUC or USS (users upload more) Example I always upload 20KB/s with USS about 25KB/s or more.
1 - this is always happening, many users (like me) test SVN builds.
2 - has been in since 2.2.1, compile latest 2.2.2 (Stable) please.
3 - sorry can't make any sense of that.
-
Sorry I'm spanish
1- Amule 2.2.2 is stable but amule can be more stable
2- Amule 2.2.2 has protocol ofuscated in KAD but can be better because is a very very important feature.
3. UBT is de amule bandwith control (is very very bad), USS or SUC are better and amule need the best control bandwith
-
2. We have PO on the same level as eMule - if we change/extend anything we will be incompatible to most of the network. Plus, PO is not intended to encrypt anything, i.e. doesn't provide any anonymity.
3. Afaik both of them are not possible for technical reasons.
-
3. Afaik both of them are not possible for technical reasons.
shame, hope something comes to light though, me needs some sort of bandwidth control.
-
i considered creating a new topic....
mods, create it in a new one if they think it would be appropriate.
better bandwidth control is essential IMO, UBT does do 'a' job but some people need a more dynamic option.
Using 'ping' is out of the question (will cause permissions and firewall problems)
I've recently read the development with 'uTorrent' and there introducing something very interesting;
<quote>
uTP, the micro transport protocol. This UDP-based reliable transport is designed to minimize latency, but still maximize bandwidth when the latency is not excessive. We use this for communication between peers instead of TCP, if both sides support it. In addition, we use information from this transport, if active, to control the transfer rate of TCP connections. This means uTorrent, when using uTP, should not kill your net connection - even if you do not set any rate limits. In addition we now implement NAT hole-punching for uTP connections, so connectivity should be improved for peers that do not have their ports mapped.
</quote>
also, I've read this protocol is being developed for use with the linux kernel
so think of it like the Wonder Shaper (http://lartc.org/wondershaper/) script, but dynamic.
discuss?
-
Also, aMule is only a little part of the network, and communication aMule <-> aMule is even less thus. So it would have no effect.