282 karma · joined October 28, 2013
I think you could probably get the IO performance you're talking about in your blog post from AWS instances or Google Cloud's local NVMe drives, but if you truly need baremetal, I'd recommend Packet or Softlayer. Don't try to run your own infrastructure or in a year you'll be: https://imgflip.com/i/1fs7it
Okay I was testing this squash pulling method, and here's the performance results I found.
Below, the tag only has VIM installed, the update installs Emacs.
First column is docker pull the next is the squash pull.
Latest pull w/o Ubuntu base downloaded: 38.1s | 19.4s
Latest pull w/ Ubuntu base downloaded: 32.8s | 18.8s
Tag pull w/o Latest downloaded: 38.3s | 21.4s
Tag pull w/ Latest downloaded: 5.7s | 20.8s
Tag pull(up to date): 2.2s | 20.1s
Tag pull(updated commit, old tag downloaded): 13s | 34.2s
Of course these values all depend on the things being installed but time differences for the tag pulls make this seem bad because it always has to download the entire commit tree.
That's probably why there's been a geographic shift to SF.
The primary value add is that if your production system is too large to run on VMs on your computer now you can develop in your prod env