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

Roadrunner cache occupies 1GB of RAM after de-serialization #3037

Closed
betalb opened this issue Apr 4, 2017 · 1 comment
Closed

Roadrunner cache occupies 1GB of RAM after de-serialization #3037

betalb opened this issue Apr 4, 2017 · 1 comment
Assignees

Comments

@betalb
Copy link

betalb commented Apr 4, 2017

Do you want to request a feature or report a bug? Bug

What is the current behavior?
Roadrunner cache is cleared only after yarn update

There is no restriction where yarn should be installed, even though officially recommended way is to install through package manager. We are using yarn on ci. It is installed into build directory which is always new and has uniq name, so roadrunner cache becomes append-only and get's increased in size after every run.

What is the expected behavior?
There should be a way to disable roardunner cache or stale data should be removed from cache.

  • cache should be scoped to yarn.js location: if cached resolutions are for yarn installed in different directory - reset. This is not ideal due to race conditions
  • or there should be a possibility to disable any writes, caches, stored in home directory
@Daniel15
Copy link
Member

Daniel15 commented Apr 7, 2017

We're going to remove the usage of Roadrunner as part of #3030

@Daniel15 Daniel15 self-assigned this Apr 7, 2017
@Daniel15 Daniel15 closed this as completed Apr 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants