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

Improve provisioning and startup performance of a dev container #1823

Closed
chrmarti opened this issue Nov 11, 2019 · 1 comment
Closed

Improve provisioning and startup performance of a dev container #1823

chrmarti opened this issue Nov 11, 2019 · 1 comment
Assignees
Labels
containers Issue in vscode-remote containers plan-item A plan item
Milestone

Comments

@chrmarti
Copy link
Contributor

No description provided.

@chrmarti chrmarti added containers Issue in vscode-remote containers plan-item A plan item labels Nov 11, 2019
@chrmarti chrmarti added this to the November 2019 milestone Nov 11, 2019
@chrmarti chrmarti self-assigned this Nov 11, 2019
@chrmarti
Copy link
Contributor Author

Senario October November
New container 10815 ms 4062 ms
Existing container 6295 ms 1547 ms
Window reload 6273 ms 435 ms
  • Using a single Dev Container with the Node.js 12 definition without extensions to install. The Docker image is in Docker's image cache. The server tar is cached on the local machine. (Avoiding downloads.)
  • Measurement is from when the resolver is called until it fulfills its Promise.
  • Average over 3 measurements.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers plan-item A plan item
Projects
None yet
Development

No branches or pull requests

1 participant