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

a cache manifest without a cache layer. Shouldn’t the layer have the highest number of requests? #20171

Open
garenwen opened this issue Mar 26, 2024 · 2 comments

Comments

@garenwen
Copy link

Is your feature request related to a problem? Please describe.
When a large concurrent pull image occurs, the get blob interface will also have a large number of database queries. Can we increase the cache and skip database queries

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe the main design/architecture of your solution
A clear and concise description of what does your solution look like. Rich text and diagrams are preferred.

Describe the development plan you've considered
A clear and concise description of the plan to make the solution ready. It can include a development timeline, resource estimation, and other related things.

Additional context
Add any other context or screenshots about the feature request here.

@wy65701436
Copy link
Contributor

the cache layer was designed for caching the manifest only, as for the blob cache, you should enable the content cache in your overall architecture, like CDN.

Copy link

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label May 31, 2024
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

2 participants