Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow axel as a download agent #156

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Allow axel as a download agent #156

wants to merge 1 commit into from

Conversation

GjjvdBurg
Copy link

Fixes #108. Allows using axel as a download agent, when this is available. The download agent can still be forced when needed.

@xdissent
Copy link
Owner

I've seen a few people request axel before, but I don't really see the benefit. All files are downloaded sequentially as they're needed, and that's just the nature of ievms, so the axel parallelism won't help anything. Additionally, curl is so ubiquitous it's nearly guaranteed to be installed already, reducing the dependency burden on the user. Am I missing something though? I appreciate the feedback regardless.

@GjjvdBurg
Copy link
Author

The main advantage of axel is that it creates multiple connections to the
download server. This can provide a significant speed up, since a single
file is essentially downloaded in parallel. I agree that curl is
ubiquitous, that's why it is kept as fallback in the patch. Allowing axel
would therefore not introduce a dependency in my view.
On Jun 21, 2013 6:40 PM, "Greg Thornton" [email protected] wrote:

I've seen a few people request axel before, but I don't really see the
benefit. All files are downloaded sequentially as they're needed, and
that's just the nature of ievms, so the axel parallelism won't help
anything. Additionally, curl is so ubiquitous it's nearly guaranteed to be
installed already, reducing the dependency burden on the user. Am I missing
something though? I appreciate the feedback regardless.


Reply to this email directly or view it on GitHubhttps://github.com//pull/156#issuecomment-19826748
.

@xdissent
Copy link
Owner

But the modern.IE servers do not support Range requests, so axel can't actually download a single file in parallel.

@GjjvdBurg
Copy link
Author

Perhaps there is some other way axel accelerates the download. I'm no
expert on how axel works, but in my small tests (screenshots attached)
there seems to be a difference in download speed. Although I do have to
admit that these tests are very far from scientifically sound, I think
they do show that there is a difference.

On 06/21/2013 08:18 PM, Greg Thornton wrote:

But the modern.IE servers do not support |Range| requests, so axel
can't actually download a single file in parallel.


Reply to this email directly or view it on GitHub
#156 (comment).

@rjmunro
Copy link

rjmunro commented Aug 15, 2013

#162 is also dependent on the server supporting range requests, and comments there imply that the modern.IE server has been updated and now does support them.

Parallel downloading can provide a large speed increase to people with high latency connections.

Another option to provide parallel downloading would be to download the different VMs in parallel. This wouldn't require range requests on the server, but would be limited to people who wanted to install more than one VM.

@xdissent
Copy link
Owner

Thanks for the heads up - I'll reassess the resume capabilities soon.

@pjkix
Copy link

pjkix commented Nov 5, 2013

can we at least set up our own CDN / mirror that supports ranges and resumes since MS doesn't seem to care about this feature? downloading these files is very very painful :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Download heavyweight files with axel, if available
4 participants