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

[fast-deps] Make range requests closer to chunk size #8681

Merged
merged 1 commit into from
Aug 4, 2020

Conversation

McSinyx
Copy link
Contributor

@McSinyx McSinyx commented Aug 2, 2020

This addresses the discovery in #8670 (comment). It is pretty stably reproducible on my network, I've run the before-after pip install tensorflow with early exit right after new resolver resolution for 3 times and the execution duration is consistent (30–31s before and 19.5–20s after patching).

Regarding the news file, I'm thinking about marking this as trivial since the feature is rather experimental and I am not entirely sure if this always make it faster for all requirement sets. If this can be merged before the bugfix release it would be nice too!

@McSinyx
Copy link
Contributor Author

McSinyx commented Aug 3, 2020

I've just added the news file as trivial. @pradyunsg, is it possible for this to land as part of 20.2.1?

@McSinyx McSinyx closed this Aug 3, 2020
@McSinyx McSinyx reopened this Aug 3, 2020
@pradyunsg pradyunsg merged commit e7357c7 into pypa:master Aug 4, 2020
@pradyunsg pradyunsg added this to the 20.2.1 milestone Aug 4, 2020
pradyunsg added a commit to pradyunsg/pip that referenced this pull request Aug 4, 2020
[fast-deps] Make range requests closer to chunk size
@McSinyx
Copy link
Contributor Author

McSinyx commented Aug 4, 2020

Thanks!

@McSinyx McSinyx deleted the faster-deps branch August 4, 2020 07:16
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants