3 ms·

I put Cloudflare in front of my portfolio, which is hosted on Github Pages, so this made me do a bit of spit take. I always just assumed that GH Pages was a sor

I put Cloudflare in front of my portfolio, which is hosted on Github Pages, so this made me do a bit of spit take. I always just assumed that GH Pages was a sort of “free perk for using Github” and that it must surely be hosted on “meh” infrastructure that would benefit from having a CDN in front. This article basically says that analysis is upside down. I’ll need to see more benchmarks with a range of methodologies before I go in and redo how my portfolio is deployed, but this sure got me started searching.

dutchmartin 6y ago
I also looked into removing Cloudflare from my github pages hosted website, but I need IPV6 support, and github pages doesn’t have that (1). Cloudflare proxies those requests to IPV4 so my website is accessible to everyone in the world. (1) https://github.community/t/cannot-reach-any-github-io-page-via-ipv6/10310/27 https://github.community/t/cannot-reach-any-github-io-page-v...
- miyuru 6y ago
  github pages had IPv6 sometime on 2017[1]. they removed after changing the IPs to one of their own. They have been dragging their feet on enabling IPv6 even on github.com and continues to be headache when working on a IPv6 only server. https://github.com/isaacs/github/issues/354 https://github.com/isaacs/github/issues/354
43920 6y ago
Github Pages uses Fastly (https://www.fastly.com/customers/github https://www.fastly.com/customers/github) as a CDN, which is pretty comparable to Cloudflare AFAIK.
em500 6y ago
Rob Pike's rules are still as relevant as ever, also for web dev: Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is. Rule 2. Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest. http://users.ece.utexas.edu/~adnan/pike.html http://users.ece.utexas.edu/~adnan/pike.html

dutchmartin 6y ago

I also looked into removing Cloudflare from my github pages hosted website, but I need IPV6 support, and github pages doesn’t have that (1). Cloudflare proxies those requests to IPV4 so my website is accessible to everyone in the world. (1) https://github.community/t/cannot-reach-any-github-io-page-via-ipv6/10310/27 https://github.community/t/cannot-reach-any-github-io-page-v...

miyuru 6y ago
github pages had IPv6 sometime on 2017[1]. they removed after changing the IPs to one of their own. They have been dragging their feet on enabling IPv6 even on github.com and continues to be headache when working on a IPv6 only server. https://github.com/isaacs/github/issues/354 https://github.com/isaacs/github/issues/354

43920 6y ago

Github Pages uses Fastly (https://www.fastly.com/customers/github https://www.fastly.com/customers/github) as a CDN, which is pretty comparable to Cloudflare AFAIK.

em500 6y ago

Rob Pike's rules are still as relevant as ever, also for web dev: Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is. Rule 2. Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest. http://users.ece.utexas.edu/~adnan/pike.html http://users.ece.utexas.edu/~adnan/pike.html