-
Notifications
You must be signed in to change notification settings - Fork 77
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
Startup performance #854
Comments
Is it a single Maven project with 50+ sub-modules? Do you need to open all those modules together, or you just need to use some of them for development? |
No submodules. Every project has it's own pom. It's roughly half services and half libraries.
Ideally they are all opened together. |
If all the projects are required to open in vscode. Maybe you can try to turn off the auto build. The side effect is that, if you turn off the auto build, you may not be able to find some errors at the first time. You need manually trigger build on demand. The setting is |
What about |
java.maxConcurrentBuilds can boost the build time. Meanwhile, you can increase the JVM memory via the setting |
We have a large monorepo (50+ Maven projects). We want to use VS Code dev containers for local development, but it takes forever to start up (i.e., import projects, etc.).
For context, our laptops are running Windows 11 and we're using Podman Desktop with WSL as the container host. We are using volumes rather than the default bind mount, which has improved performance. We are building the images locally which also decreases the time it takes to create or rebuild a dev container.
On a fresh volume the initial import takes a very long time. Maybe 2 hours? Just a guess. Reloading the window or rebuilding the container also takes a long time. Maybe 30 minutes - 1 hour?
Is this expected? Is there anything we can do to improve performance?
The text was updated successfully, but these errors were encountered: