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

Allow to set an alba fragment cache size limitation per vPool #564

Open
wimpers opened this issue Jan 11, 2017 · 1 comment
Open

Allow to set an alba fragment cache size limitation per vPool #564

wimpers opened this issue Jan 11, 2017 · 1 comment
Milestone

Comments

@wimpers
Copy link

wimpers commented Jan 11, 2017

Currently an alba fragment cache is shared between all vPool that are configured to use that SSD backend. As each vPool is a different customer it would be good to limit the amount of space (in %) the vPool can consume in the fragment cache. This size limitation should be dynamically updateable so you don't have to restart the proxy in case new SSD are added to the backend.

Adding such a limitation would require:

  • have a different prefix (for cache namespaces) per vpool
  • periodically refresh how much space all cache namespaces with this prefix occupy
  • do eviction per vpool
@wimpers
Copy link
Author

wimpers commented Apr 3, 2017

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

No branches or pull requests

1 participant