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

throttle project initialization #389

Closed
kanej opened this issue Feb 7, 2023 · 0 comments · Fixed by #395
Closed

throttle project initialization #389

kanej opened this issue Feb 7, 2023 · 0 comments · Fixed by #395
Labels
status:ready This issue is ready to be worked on type:improvement Improvement existing feature

Comments

@kanej
Copy link
Member

kanej commented Feb 7, 2023

We have reports of high resource usage in repositories with a large number of hardhat projects.

We currently initialize all projects in parallel. To lessen the peak load we should throttle the number of in-parallel project initializations. This will extend the time to get to a fully setup language server, but flatten the curve of cpu/memory usage.

It is an open question whether the throttling mechanism should be limited to hardhat projects or all projects (hh projects create a thread per project).

@kanej kanej moved this to Todo in hardhat-vscode Feb 7, 2023
@kanej kanej added this to the Developer framework agnostic milestone Feb 7, 2023
@kanej kanej added type:improvement Improvement existing feature status:ready This issue is ready to be worked on and removed status:triaging labels Feb 7, 2023
@antico5 antico5 moved this from Todo to In Review in hardhat-vscode Feb 15, 2023
kanej pushed a commit that referenced this issue Feb 22, 2023
@github-project-automation github-project-automation bot moved this from In Review to Done in hardhat-vscode Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:ready This issue is ready to be worked on type:improvement Improvement existing feature
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant