Jump to content

rafi

Established Members
  • Posts

    8,960
  • Joined

  • Last visited

  • Days Won

    148

Posts posted by rafi

  1. alus:

    Hm, well can you prove that a previous version of uT on the same torrent gets a full set of peers? The only change around there recently was the fix to the half-open limiter, which does make connect attempts take a bit longer to time out (but hey, it doesn't bust the half-open limit )

    well, 1.8 and 1.7.7 seems to behave the same. So, it might be one of my setups... I remember it was not like that ... I really don't understand it., since it does reach higher connections # (like 220/400) so why is it stuck @~150 when the limit is 200... :(

  2. edit(2):

    If you ask me, my ISP is not relevant to this issue (yes, he is terrible, but the best we have here...) . And you don't have to trust my report(s), you can try it yourself and try understand the symptom, and deduct why uT does not reach the specified max peers. Yes, avarage peers' speed IS slow here (~1-8K also due to 200-300 msec latency to the US). So what ? uT should handle this situation as well as it does connecting to closer/faster peers.

    and here is a speed<->peers graph for you (alus... ):

    73963900nt7.png

    w697.png

  3. 20 ? ... are you sure ? isn't it too small a value for any deductions ? ... :) I'll try and edit the result it into here

    edit:

    well, for 20 it reaches 20 in a few seconds and stays with 20 ... BUT ... my poor DL speed is 15K instead of ~100K with 200 ....

    What does this means for you ? I think your algorithm should let me decide how to reach my best speed, and I should be able to trust uT to reach the max values I set for # of peers.

  4. For some reason, I have the feeling that uTorrent does not stabilizes around the maximum number pf peers defined per torrent. I have set it to 200, and got around 150 . I'm now trying to set it to 300, and getting around 200-220. Available seeds/peers for that torrent is now ~ 1700/5000. Is there some issue with the # of connections+limit algorithm ?

    PEX + DHT are on.

  5. no, since DHT was disabled as well (as you can see on the status bar...). So was PEX. BUT you are right... I forgot about RSS. I have about 12 feeds scanned every 20 min. I'll turn this off and wait&see again...

    edit:

    strange... another bug... tried to set RSS interval (rss.update_interval) to 201234 and it was set to 10 min... :)

    well. I'll just add this to my RSS features&bugs list here ... http://forum.utorrent.com/viewtopic.php?pid=352646#p352646 ;)

    edit(2):

    well, I cannot get RSS interval to work at all... is it broken ? It always 10 min ...

  6. I'm having no such issue at all. I get a small ~30 secs/ <1K activity every 5/15 minutes and 0 otherwise. I don't think this small amount should have a significant effect on your limits... but it is interesting what causes it.

    16793173zw0.png

  7. isn't this more suitable for the features' request thread?...

    edit:

    Also a small issue with the main view - if you have a long list of rss feeds and scroll + select one at the bottom, then exit from uTorrent - when you run it next time - it remembers the selection correctly, but you cannot see the selected feed since it does not auto-scroll to it.

  8. add RSS feed button, edit feed (from context menu) and create new torrent button - all pop up multiple dialogs when clicked more then once. Add torrent from URL - pops only one when clicked more then once. Is it a bug ? In sake of consistency - shouldn't all behave "one at a time" ?

×
×
  • Create New...