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

Implement the more granular build cache #6413

Open
galargh opened this issue Feb 26, 2025 · 0 comments
Open

Implement the more granular build cache #6413

galargh opened this issue Feb 26, 2025 · 0 comments
Labels
status:ready This issue is ready to be worked on v-next A Hardhat v3 development task

Comments

@galargh
Copy link
Member

galargh commented Feb 26, 2025

As the result of #5991 (https://www.notion.so/nomicfoundation/solidity-compilation-cache-17b578cdeaf580e3ba10c0d907fd6a4d), we cache compiler outputs per compilation job ID.

This is an optimal caching strategy for builds that do not merge compilation jobs (compilation job per root file) and builds in which none of the sources change.

As a follow-up, our cache should work effectively for builds in which only a subset of files being compiled change.

One possible solution to this, briefly explored during the initial cache implementation, is caching based on unmerged jobs. A POC of this solution was implemented in v-next...build-system-cache-v2

The next step on this is to create a design doc and open up a discussion about the implementation and required performance optimizations.

@github-actions github-actions bot added the status:ready This issue is ready to be worked on label Feb 26, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Hardhat Feb 26, 2025
@kanej kanej moved this from Backlog to To-do in Hardhat Feb 27, 2025
@kanej kanej added this to the Public Alpha Feature Rollout milestone Feb 27, 2025
@kanej kanej added the v-next A Hardhat v3 development task label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:ready This issue is ready to be worked on v-next A Hardhat v3 development task
Projects
Status: To-do
Development

No branches or pull requests

2 participants