distribution/configuration
Liang Zheng a2afe23f38 add concurrency limits for tag lookup and untag
Harbor is using the distribution for it's (harbor-registry) registry component.
The harbor GC will call into the registry to delete the manifest, which in turn
then does a lookup for all tags that reference the deleted manifest.
To find the tag references, the registry will iterate every tag in the repository
and read it's link file to check if it matches the deleted manifest (i.e. to see
if uses the same sha256 digest). So, the more tags in repository, the worse the
performance will be (as there will be more s3 API calls occurring for the tag
directory lookups and tag file reads).

Therefore, we can use concurrent lookup and untag to optimize performance as described in https://github.com/goharbor/harbor/issues/12948.

P.S. This optimization was originally contributed by @Antiarchitect, now I would like to take it over.
Thanks @Antiarchitect's efforts with PR https://github.com/distribution/distribution/pull/3890.

Signed-off-by: Liang Zheng <zhengliang0901@gmail.com>
2024-04-26 22:32:21 +08:00
..
configuration.go add concurrency limits for tag lookup and untag 2024-04-26 22:32:21 +08:00
configuration_test.go add concurrency limits for tag lookup and untag 2024-04-26 22:32:21 +08:00
fuzz_test.go Fuzzing: Rewrite existing fuzzers to native go fuzzers 2022-11-12 17:30:10 +00:00
parser.go Fix the code and update tests that verify the new code works 2023-07-17 22:40:32 +01:00
parser_test.go testing: replace legacy gopkg.in/check.v1 2023-12-13 09:22:43 +00:00