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
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
At the minute, each scan of our local image manifests involves a large number of memcache requests (one for tags, then one for each tag). It'd be nice to be able to just fetch one thing; when we've managed to assemble a whole set of data, we can regenerate it.
The text was updated successfully, but these errors were encountered:
The reason for doing it this way was so that it matches the flow of getting information from a remote repository.
E.g. we have to make an individual HTTP call to get the manifest for each tag.
I think it would complicate the code if we had a different scheme for memcache. So I would only consider this if there was a clear benefit for doing so (i.e. performance).
(But it is just an idea. I agree that unless it's demonstrably a problem in practice, which I only suspect at this time, we shouldn't hurry to look into this)
At the minute, each scan of our local image manifests involves a large number of memcache requests (one for tags, then one for each tag). It'd be nice to be able to just fetch one thing; when we've managed to assemble a whole set of data, we can regenerate it.
The text was updated successfully, but these errors were encountered: