Skip to content

registry: add ability to customize the number of concurrent connections to registries#6769

Open
jsternberg wants to merge 1 commit into
moby:masterfrom
jsternberg:configurable-registry-concurrency
Open

registry: add ability to customize the number of concurrent connections to registries#6769
jsternberg wants to merge 1 commit into
moby:masterfrom
jsternberg:configurable-registry-concurrency

Conversation

@jsternberg
Copy link
Copy Markdown
Collaborator

The current number of concurrent connections to registries is currently
set at 4 and it is unconfigurable. If you want to do more, it's currenly
not possible. This configuration change allows a person to customize the
number of connections that will be allowed concurrently through the new
concurrency section of the configuration. At the moment, the only
option there is concurrency.registry.max-connections which changes the
maximum number of push/pull operations to registries.

Replaces #6517.

…ns to registries

The current number of concurrent connections to registries is currently
set at 4 and it is unconfigurable. If you want to do more, it's currenly
not possible. This configuration change allows a person to customize the
number of connections that will be allowed concurrently through the new
`concurrency` section of the configuration. At the moment, the only
option there is `concurrency.registry.max-connections` which changes the
maximum number of push/pull operations to registries.

Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
Copy link
Copy Markdown
Member

@tonistiigi tonistiigi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because it is global, why can't we do it with just the variable update like in the previous PR instead of all this complexity.

@jsternberg
Copy link
Copy Markdown
Collaborator Author

I guess we could. It just seemed strange to me to modify a global variable based on a configuration value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants