-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add cache manager extension #251
base: master
Are you sure you want to change the base?
Conversation
9424c79
to
9f0582c
Compare
charts/extensions/charts/cache-manager/templates/cache-manager.yaml
Outdated
Show resolved
Hide resolved
9f0582c
to
385c911
Compare
385c911
to
1628335
Compare
return | ||
|
||
logger.info(f'Current cache size: {bytes_to_str(size)}') | ||
logger.info(f'Max cache size: {bytes_to_str(cfg.max_cache_size_bytes)}') |
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.
maybe for future pullrequest: should we expose cache-metrics (e.g. for prometheus)?
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 think that could also be something we could add to the delivery-service, i.e. adding information on cache hits/misses to prometheus.
1628335
to
ce06432
Compare
ce06432
to
ebc541b
Compare
The cache manager's purpose in this first iteration is to cleanup the persistent db cache according to the supplied configuration via the scan configuration CR. If the configured `max_cache_size_bytes` is exceeded, cache entries are removed according to the configured weights in the `cleanup_strategy` cache strategy property until the cache size reaches `max_buffer_bytes` again.
ebc541b
to
d39c94d
Compare
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: