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

Very slow builds on CI machine #370

Open
buhrmann opened this issue Sep 27, 2023 · 0 comments
Open

Very slow builds on CI machine #370

buhrmann opened this issue Sep 27, 2023 · 0 comments

Comments

@buhrmann
Copy link

buhrmann commented Sep 27, 2023

Hi,
I'm curious about great differences in build times for a package of mine (using conda mambabuild), between my local machine (macOS Arm M1), and a CI machine.

The greatest time seems to be spend on "Reloading output folder" steps. E.g. locally:

...
17:39:42 > #12 0.973 Attempting to finalize metadata for grapy-core
17:39:42 > #12 0.973 INFO:conda_build.metadata:Attempting to finalize metadata for grapy-core
17:39:48 > #12 6.455 Reloading output folder: /opt/conda/conda-bld
17:39:48 > #12 6.497 Reloading output folder: /opt/conda/conda-bld
17:40:30 > #12 48.90 Reloading output folder: /opt/conda/conda-bld
17:40:30 > #12 49.11 BUILD START: ['grapy-core-0.1.0-py_16.tar.bz2']
17:40:30 > #12 49.11 Reloading output folder: /opt/conda/conda-bld
17:40:32 > #12 50.76
17:40:32 > #12 50.76 ## Package Plan ##
...

where 42s of the total build time of 2:40s is spend on a single reload step.

And In CI it's much worse:
image

Here, the same reload step takes a whopping 166s, i.e. almost 3 min. And the total build takes more than 7 min, instead of the 2:40s locally.

Do you have any experience with such differences depending on the machine/environment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant