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

Improve project init performance #5844

Open
10ko opened this issue Mar 18, 2024 — with Linear · 0 comments · Fixed by #6002 · May be fixed by #5920
Open

Improve project init performance #5844

10ko opened this issue Mar 18, 2024 — with Linear · 0 comments · Fixed by #6002 · May be fixed by #5920
Assignees

Comments

Copy link
Member

10ko commented Mar 18, 2024

Click here to see the initial problem statement.

Initial problem statement.

For very large projects, we've seen the hashObject method on GitHandler being a performance bottleneck that substantially slows down initialization.

We're looking into an opt-in local cache for file hashes to speed up subsequent project scans—this issue tracks that work (see #5920 — this can optimise a very specific scenario, not a super-critical improvement).

Workaround

Unnecessary object hashing can be avoided by excluding untracked files from a Garden project. The preferred way is to use .ignorefile.

Problem statement.

For large projects, Gardn performs the full graph resolution before execution any actions. This can be optimized by doing partial graph resolution if the target actions are explicitly specified in the command.

The initial solution is available in #6002.

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