You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: