Oh great, thanks!
On Wed, 8 Jun 2016 at 03:52 Maciej Szulik wrote:
> We're hoping to gain some improvements in that area once the distribution
> rebase lands [1].
> distribution v2.4.0 change s3 storage driver to native aws s3 client [2]
>
> Maciej
>
> [1] https://github.com/openshift/origin/pul
We're hoping to gain some improvements in that area once the distribution
rebase lands [1].
distribution v2.4.0 change s3 storage driver to native aws s3 client [2]
Maciej
[1] https://github.com/openshift/origin/pull/8938
[2] https://github.com/docker/distribution/releases/tag/v2.4.0
On Sun, Jun
Good point on encryption. Disabling encryption which I believe is done
outside of the registry (as an AWS KMS key is used) has improved
performance dramatically.
On Sun, 5 Jun 2016 at 05:40 Clayton Coleman wrote:
> In general, S3 should be as efficient for the registry than EBS, and far
> more o
In general, S3 should be as efficient for the registry than EBS, and far
more operationally easy (it also scales out horizontally).
I don't know whether the encrypt option is done on the registry side - have
you compared running with or without?
It's currently fairly difficult to move between bac
Hi,
Does anyone have any comparisons of s3 registry performance? We've found it
to be quite slow, at least 2-3 times longer then using something like an
EBS volume. Here's the config being used:
encrypt: true
secure: true
v4auth: true
chunksize: 26214400
I stumbled across
