Vscode-remote-release: Improve provisioning and startup performance of a dev container

Created on 11 Nov 2019  路  1Comment  路  Source: microsoft/vscode-remote-release

containers plan-item

Most helpful comment

| 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.

>All comments

| 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.
Was this page helpful?
0 / 5 - 0 ratings