amp

Member
  • Content count

    299
  • Joined

  • Last visited

Posts posted by amp


  1. Then it should have another description.

    So, you won't make it in easy way.

    Let me state current problems again:

    - Download speed decreases a lot if other side (sources) is on slow connection. Even if it could be faster.

    - Download speed might stuck at all, if all sources were dropped and last source goes offline.

    So, as void mentioned above, you may change your dropping algorithm in case of high priority downloads.

    Or you may add an "autoretry source" to automaticly readd a dropped source after some time or on some event (another source goes offline).

    Or you may try to add "training" to explore real connection speed of the host. There are some online tools which can do so. You may also monitor current speed and approximate it to real - higher math techniques available ;).


  2. Leeching is about downloading without uploading, AFAIR.

    A lot of people thinks that if they download one file from five users then the the slots will be released 5x sooner, but it's closed to true only on really fast connections.
    I think that it tends to be on *any* connection. You have download slots limiting after all.

    Hot discussion about one simple edit ;)

    if(autoDrop) vs if(autoDrop && enabledSlowDisconnecting)

    Question appears - what for we have "Enable slow downloads disconnecting" option if it's enabled in any case.

    It's hard to me to explain it in English

    Unfortunelly I do not understand czech, only russian and english :)


  3. Your logic about leeching ain't clean enough to me.

    You see, I have 1M/1M connection which is relatively fast to our community - most have from 256/128 to 1024/256, but first is the most.

    So, almost every source is slow to me. And they can't become faster because of dropping sources. So, I'm a seeder who cannot download as fast as it actually possible ;). At my point of view, this feature is not anti-leeching, but anti-downloading. After all, faster I get a file, faster I will seed it! Even I would be on 256/128 this remain true.

    I like torrents, because they fast, do not have slots and stupid limits, but they really suck in sharing of lotta things. Doing torrent for every one file :-/.

    Crise

    Better tell us your point of view about all this things :)


  4. Whats the difference between slow and fast connection in the segment downloading algorithm? Some hardcoded constants?

    At my point of view, segmented downloading helps to maximize efficiency of up and down bandwidth usage! No matter how fast you are. So, as far as this algorithm should stay not for speed, but efficiency, it should be tunable for any types of connections. Bring us fine tune settings!


  5. Ok, StrongDC project's main page.

    Safe segmented downloading Download one file from more users simultaneously without corruption! This way of downloading dramatically improves download speed, especially for fast connections, and it's safer than classical downloading.

    So, this is why we're still using your software. Because segmented downloading allows us to improve download speed! We have a problem. A problem which CAN be solved.

    And all you can say is "f**k off guys, buy a good internet access, not my business". Good point. Next time someone will say your software takes lot of CPU, say, that their PCs are crap, and you can't do anything with this. And you would be damn right.

    I hope ApexDC developers won't be so selfish.


  6. How about making priority adjustment setting into Apex? Say, you need to work with over tools. Then, you just set low priority, so even if it take much CPU usage for some reason (checking TTH or so on), it won't slow down a lot .


  7. I believe DC is still more about community and sharing, than downloading as fast as you can.
    Oh, believe me, download 4Gb file with 3Kb/s with constantly droping sources is REALLY annoying.

    You see, we have not much fast speeds here, actually, most people on our hub have 256/128 connection speed. And we should open 5 slots as it mentioned in our hub rules. So, most sources have speed about 1-2 Kb/s.

    no, it can't, because it removes source only if there's other downloading source

    void can explain better, he made more investigation into this problem. I saw such behaviour, then all sources are dropped :-/.


  8. How about not just displaying free slots, but also display number of users in upload queue? You may update it every 10 minutes, for example, to not to spam much.

    I've noticed, that free slots are also shown in search results on any client. Have looked deep into sources, but may it also possible to show free slots for every users (active way), not only Apex?