Skip to content

build: set opt-level to 1 only in CI#9061

Open
martinvonz wants to merge 1 commit intomainfrom
mz/szktsuwtvsny
Open

build: set opt-level to 1 only in CI#9061
martinvonz wants to merge 1 commit intomainfrom
mz/szktsuwtvsny

Conversation

@martinvonz
Copy link
Member

Incremental builds have gotten painfully slow since I set opt-level=1 in cb81f0e. They take around 3 minutes for me on a pretty fast machine. Let's go back to using the default opt-level of 0 in the dev profile and use an opt-level of 1 only in CI tests.

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added/updated tests to cover my changes
  • I fully understand the code that I am submitting (what it does,
    how it works, how it's organized), including any code drafted by AI
  • For any prose generated by AI, I have proof-read and copy-edited with an
    eye towards deleting anything that is irrelevant, clarifying anything that
    is confusing, and adding details that are relevant. This includes, for
    example, commit descriptions, PR descriptions, and code comments.

Incremental builds have gotten painfully slow since I set
`opt-level=1` in cb81f0e. They take around 3 minutes for me on a
pretty fast machine. Let's go back to using the default opt-level of 0
in the dev profile and use an opt-level of 1 only in CI tests.
@martinvonz martinvonz requested a review from a team as a code owner March 8, 2026 20:53
@higgsd
Copy link
Contributor

higgsd commented Mar 8, 2026

Yes please 😀

Comment on lines -171 to -174
[profile.dev]
# Opt-level 0 tends to run out of stack on Windows when running async code
opt-level = 1

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this at least be conditionalized on Windows? Also, maybe by moving all our dependencies to opt-level=3 (ref #9009) we might get better stack usage through some inter-crate optimizations? I'm not sure. Maybe you can just try deleting this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe Windows users would want to increase the stack size than waiting for slow compilation?

BTW, I feel the opt-level=3 change also impacted build time, but I haven't measured the difference.

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

Successfully merging this pull request may close these issues.

4 participants