You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the compute node image, the build clones the full 'azure-sdk-for-rust' repository, with history and all. The repository is about 300 MB in size, so we download that 300 MB on every CI run. I noticed this when building locally; it slows down the local docker build significantly too.
Note how the "update azure-sdk-for-rust repository" step took about 150 s.
Proposed solution
Ideally, cargo build would make a shallow clone of the repository; the build doesn't actually need the history. A shallow clone would be only about 1 MB. There's an unstable cargo feature to use a different library for downloading git dependencies, which would do just that and fix this issue. Unfortunately it's unstable so it doesn't help us right now. I tested it locally though and it's great.
One easy quick fix we could do is to create a branch in our 'neondatabase/azure-sdk-for-rust' repository which would not include the history, and use that in the CI.
The text was updated successfully, but these errors were encountered:
Yeah it's quite slow indeed (and there is no progress indicator or anything).
Ideally the SDK fork is temporary, see #10404. But in the meantime I suppose we could try out making a new branch with the history reset in the meantime. I'll make a PR to test if it improves things.
The problem
When building the compute node image, the build clones the full 'azure-sdk-for-rust' repository, with history and all. The repository is about 300 MB in size, so we download that 300 MB on every CI run. I noticed this when building locally; it slows down the local docker build significantly too.
Here's one example run from CI:
Note how the "update azure-sdk-for-rust repository" step took about 150 s.
Proposed solution
Ideally,
cargo build
would make a shallow clone of the repository; the build doesn't actually need the history. A shallow clone would be only about 1 MB. There's an unstable cargo feature to use a different library for downloading git dependencies, which would do just that and fix this issue. Unfortunately it's unstable so it doesn't help us right now. I tested it locally though and it's great.One easy quick fix we could do is to create a branch in our 'neondatabase/azure-sdk-for-rust' repository which would not include the history, and use that in the CI.
The text was updated successfully, but these errors were encountered: