RejZoR, on 25 September 2012 - 02:35 PM, said:
Something really weird is going on here. It took ages to connect to KAD from yellow to green and most of the time i was not at home it was uploading at 30-40KB/s out of 100KB/s possible. Now that i woke up the monitor the upload also started raising. Not to mention clients on queue. 99 where i'd usually have over 600 at the same time of running kMule. Something isn't quite right here...
EDIT:
This is rubbish. Last build was sometimes quirky but this one is horrible. 90% of the time it's using just 20% of my entire upload capacity for no reason at all. How am i suppose to keep me ratio up if the client decides not to upload anything. Queue is also basically empty 99% of the time. Several hours of runtime and just a hair over 30 clients in queue. Last build almost instantly got over 500... makes no sense to me.
I'm sorry to hear that, I just can say that both tux and I are testing the builds and it's working properly for us, though none of us has a fast line (>80kB/s ul) - we'll check for possible problems, though.
Quote
Now i'm not even sure anymore what's going on. It seems like KAD is protesting. Is there no way of performing upload on KAD only by getting it populated on KAD faster? It seems like it's taking freakin ages to get in touch with other clients if you're not also downloading something. If you do, upload fills quickly. If you don't, it goes nowhere. Can't this be changed in any way so that it would show the files quicker to other users?
Well, yes, unfortunatelty, publishing takes some time... we could promote our files by "faking" downloading but I fear that this would cause too much overhead.
DavidXanatos, on 26 September 2012 - 03:14 PM, said:
What do you think about adding NAT-Travesal from neoMule ?
this feature may give you an real edge over the official mule.
Na, I don't know... we would have to try it "in the wild" and it's HEAVY change, including the necessity for additional protocol extensions... but we'll see.