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

Speed up compilation times by going over recommendations in this article. #5273

Closed
5 tasks done
dessalines opened this issue Dec 19, 2024 · 3 comments
Closed
5 tasks done
Labels
enhancement New feature or request

Comments

@dessalines
Copy link
Member

Requirements

  • Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a feature request? Do not put multiple feature requests in one issue.
  • Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.
  • Do you agree to follow the rules in our Code of Conduct?

Is your proposal related to a problem?

I recently found this article which has a few recommendations for speeding up compilation times. Its worth trying some of them out.

Article: https://corrode.dev/blog/tips-for-faster-rust-compile-times/

Describe the solution you'd like.

NA

Describe alternatives you've considered.

NA

Additional context

No response

@dessalines dessalines added the enhancement New feature or request label Dec 19, 2024
@Nothing4You
Copy link
Collaborator

I think a major time sink in the CI pipeline is that it currently doesn't preserve any data between the steps, which means build cache is not retained.
I looked into this before but it doesn't seem like woodpecker has any good mechanism for that.

@Nutomic
Copy link
Member

Nutomic commented Dec 20, 2024

@Nothing4You It does actually preserve data between steps, thats what CARGO_HOME: .cargo_home on each step is for. Without that parameter it downloads and compiles deps for each step again. Though at the moment we are not caching build data across CI runs, iirc we disabled it because it caused more trouble than it was worth.

@Nutomic
Copy link
Member

Nutomic commented Jan 10, 2025

Done in LemmyNet/lemmy-docs#341

@Nutomic Nutomic closed this as completed Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants