Skip to content

Conversation

@Madieyeee
Copy link

Summary

This PR introduces a lightweight and backward-compatible caching mechanism to the install_deps.sh script.
The goal is to significantly reduce repeated dependency installation time in local and CI/CD environments.

Motivation

Currently, every execution of install_deps.sh re-runs the full dependency installation process, even when all required packages are already present.
This causes unnecessary waiting time and redundant network calls, especially in continuous integration environments where the script may run multiple times per workflow.
This patch solves that inefficiency by caching previously installed packages.

Changes Introduced :
Dependency caching system via a persistent file at ~/.folly_deps_cache
Already-installed packages are skipped automatically
Cache updates dynamically after each successful installation
Added --clear-cache flag to reset the cache manually
Added --yes / -y flag for non-interactive runs (CI-friendly)
Clear [CACHE] and [INSTALL] logs for better visibility
Idempotent behavior — script can be safely re-run multiple times

Benefits
Environment : Developer local run | Before : it Installs all packages each time | After : it Skips cached ones instantly

This patch introduces a lightweight caching mechanism to avoid reinstalling already satisfied system packages.
It improves build times significantly on repeated executions, especially in CI/CD pipelines.
Features include:
[ Persistent cache file (~/.folly_deps_cache)
--clear-cache and --yes options
Backward-compatible with existing scripts
Up to 40–60% faster dependency resolution on repeated runs. ]
@meta-cla
Copy link

meta-cla bot commented Oct 11, 2025

Hi @Madieyeee!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla meta-cla bot added the CLA Signed label Oct 12, 2025
@meta-cla
Copy link

meta-cla bot commented Oct 12, 2025

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant