-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add Aspera CLI download support to pipeline #259
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code itself is fine.
But this is a major behavioural change of the pipeline, do we want to bundle it with the tags and template stuff? Given it's a new feature I'd want to add it to the next release.
Yep, this should be fine. We have a bunch of other bug fixes / features included in this release too. To be honest, not sure when we are going to get around to updating this pipeline again so may as well do it now. We just need to get it done now because it's been dragging. |
Closes #68
New parameter:
--force_ftp_download
to force FTP downloads.I have set Aspera to be the new default for downloading data. I am not aware of any obvious limitations at this point with doing this so it feels right because it is lightning-fast compared to FTP and will allow users to report back issues quicker. We can revert this back to using FTP in the future quite quickly if needed.
I have run some full-sized tests on AWS and Azure comparing Aspera download times to FTP and we see a 50% speed-up in pipeline completion: