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

Request to Use Axel instead of Wget for Exporters #127

Open
v2thegreat opened this issue Oct 11, 2019 · 2 comments
Open

Request to Use Axel instead of Wget for Exporters #127

v2thegreat opened this issue Oct 11, 2019 · 2 comments

Comments

@v2thegreat
Copy link

Hey! I noticed that the download speed for the exporters was a bit slow compared to what we've seen be used in our pipeline. Have you considered using something like Axel that'll parallelize the downloads across multiple threads? I see that this is something that's already done here, but there is Pythonic overhead involved that might be better utilized somewhere else.

Looking at how you've done it in src/exporters/chirps.py, it seems that it should only require modifying this line to speed up the downloads with the correct configuration of axel to get the same results.

Finally, seeing as how downloading the data is an important part of the pipeline, it might help speed up the overall process substantially as the project grows to include other datasets as needed in the future.

@gabrieltseng
Copy link
Contributor

Hi!

Axel seems very interesting - we'll take a look! We do want to minimize the amount of dependencies in the pipeline, so we might not integrate axel straight away.

Thank you!

@tommylees112
Copy link
Contributor

This is really great of you to take an interest in the pipeline @v2thegreat ! Do you work with environmental data often? How would you like to use the pipeline?

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

No branches or pull requests

3 participants