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.

Sign up for GitHub

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

Jump to bottom

Use dedicated ThreadPool for Futures (for remote fetch / push) #31

Closed
jlprat opened this issue Jun 20, 2023 · 0 comments
Closed

Use dedicated ThreadPool for Futures (for remote fetch / push) #31

jlprat opened this issue Jun 20, 2023 · 0 comments
Labels
3.3 Related specifically for 3.3 Stale

Comments

@jlprat
Copy link
Member

jlprat commented Jun 20, 2023

Current 3.3 branch uses the shared thread pool for doing remote fetch (or push), we should follow suit of what upstream is doing and use a dedicated thread.
@jlprat jlprat added the 3.3 Related specifically for 3.3 label Jun 20, 2023
@github-actions github-actions bot added the Stale label Sep 19, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3.3 Related specifically for 3.3 Stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jlprat