Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

Thread: Slow Donwloads. 6 Mbit. Should take 2 hours

  1. #11

    Thumbs up Solved :D - ARIA did the trick !

    I used 12 connections in 10MB packges while using WGET and ARIA won the race.


    Code:
    aria2c --max-connection-per-server=12 --min-split-size=10M <URL>
    (1024*2)/64=32MB per Split.

    (1024*A)/B*4, where A = File size, and B = Max of connections allowed.

    What do you think of that model ?

    Code:
    aria2c --max-connection-per-server=16 --min-split-size=32M
    Cheers

  2. #12
    Jim Henderson NNTP User

    Default Re: Slow Donwloads. 6 Mbit. Should take 2 hours

    On Fri, 27 Jun 2014 20:06:01 +0000, binarydepth wrote:

    > What do you think of that model ?


    Ultimately, I think if the model maxes out your connection speed, it's a
    good model.

    Jim



    --
    Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
    Novell/SUSE/NetIQ Knowledge Partner

  3. #13

    Default Re: Slow Donwloads. 6 Mbit. Should take 2 hours

    Quote Originally Posted by Jim Henderson View Post
    On Fri, 27 Jun 2014 20:06:01 +0000, binarydepth wrote:

    > What do you think of that model ?


    Ultimately, I think if the model maxes out your connection speed, it's a
    good model.

    Jim



    --
    Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
    Novell/SUSE/NetIQ Knowledge Partner
    Aria should tell that if it doesn't. Don't you think ?

    Of course many CLI users have enough common sense. I'm biased to precision but Aria would stop if the download already finished.

  4. #14
    Jim Henderson NNTP User

    Default Re: Slow Donwloads. 6 Mbit. Should take 2 hours

    On Sat, 28 Jun 2014 03:56:02 +0000, binarydepth wrote:

    > Aria should tell that if it doesn't. Don't you think ?


    It's difficult to judge how much bandwidth is available. TCP doesn't
    work like that - it has some built-in dynamic throttling based on whether
    or not a request is sent and a response isn't received, but there's no in-
    built way for the software to ask "how fast is my connection?". That's
    why (for example) torrent speed throttling by the client is inexact; it
    operates by denying the inbound data a response, so the sender will
    throttle back on how fast the data is being sent in order to cut down on
    retransmissions.

    It also depends on how many concurrent connections the server is
    configured to permit overall and per client. You might want to open 12
    connections to the server, but if the server only permits 4 per client,
    then you're not going to get an optimal speed over 12 connections.
    Similarly, if the server is configured to limit the amount of outbound
    data being sent to an individual connection or to a specific client,
    that's also a factor.

    As are the network links between you and the server. I guarantee you
    that if you have a 30 Mbps connection (as I do) and you connect to a
    server that's got 10 Mbps or 100 Mbps worth of bandwidth available to it,
    but there's a high-latency 56 Kbps link between you and the server,
    you're not going to max out your connection.

    The same is true even if you have a full 30 Mbps between you and the
    server, unless you have a dedicated connection to that server, because
    other people are using that bandwidth as well.

    It's not such a simple problem to solve, because networks aren't simply
    constructed.

    > Of course many CLI users have enough common sense. I'm biased to
    > precision but Aria would stop if the download already finished.


    Naturally it would stop if the download was done - there would be no more
    data to send.

    Jim

    --
    Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
    Novell/SUSE/NetIQ Knowledge Partner

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •