-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat: SQLite-based package cache #26608
feat: SQLite-based package cache #26608
Conversation
Cold Start
Warm Start
(Apple M1 16Gb) |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it, how to distribute it for multiple runners? or when a single runner is running on different hosts? 🤔
I think this can be for one instance only |
Co-authored-by: Michael Kriese <[email protected]>
Use sqlite-native time function instead of |
normally sqlite can handle multiple processes accessing the same database |
# Conflicts: # package.json # pnpm-lock.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Log when initializing too. Ideally logging if an existing one was found or new one created
Co-authored-by: Michael Kriese <[email protected]>
Co-authored-by: Michael Kriese <[email protected]>
🎉 This PR is included in version 37.160.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Co-authored-by: Michael Kriese <[email protected]>
Changes
Additional
useSqliteCache
option could enable usage of SQLite for package cache, instead of file-based one (cacache)Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: