4 ms·
So excited for Registry 2.0, the slowness of the current registry is a real pain point. Anyone who writes an article benchmarking the two against each other wil
by omni 12y ago
So excited for Registry 2.0, the slowness of the current registry is a real pain point. Anyone who writes an article benchmarking the two against each other will receive my upvote.
- Sirupsen 12y agoWe put our registries behind a caching Nginx, also has the nice side-effect of HA if you push to all of them.
- deleted 12y ago[deleted]
- toomuchtodo 12y agoBehind ELBs with S3 as the backend store is where its at :)
- omni 12y agoThat is actually how I'm deployed right now. Still pretty slow, and S3 has its own downsides (mostly you can get false 404s after you've pushed an image but before it's fully propagated).
- toomuchtodo 12y ago> and S3 has its own downsides (mostly you can get false 404s after you've pushed an image but before it's fully propagated). Only happens in us-east-1 due to it having eventual consistency (whereas all other S3 regions have read-after-write consistency). Use another region and the false 404s will go away. http://shlomoswidler.com/2009/12/read-after-write-consistency-in-amazon.html http://shlomoswidler.com/2009/12/read-after-write-consistenc...