Why can't GitHub employ the DDOS mitigation behavior only during an active DDOS attack? I assume such attacks are not that frequent; perhaps once a week at most?
GitHub Pages with a custom root domain is slow
41–50 of 93 posts
Re: GitHub Pages with a custom root domain is slow
#42Can someone explain how "Visitors to this site’s index page have an average page load time of 3.5 seconds. 70% of those are here for the first time. 3.5 ÷ 70% = 5. So first time visitors have an average page load time of 5 seconds." makes any kind of mathematical sense? If only 10% of visitors were first time, would that mean their average page load speed was 35 seconds? This is some crazy use of the word "average".
The assumption is that repeat visitors have a load time of 0.
Re: GitHub Pages with a custom root domain is slow
#43Earlier quoted context omitted.
That's not necessarily true. My own site is a Jekyll site. To host that on S3, I'd need to generate it first and upload the generated files as opposed to my source files. Now that's not really a big deal, but I do enjoy the convenience of only having to do a `git push` to deploy my site on Pages. That being said, I notice times similar to another commenter above, around 1-2s usually. I don't think I've seen a five se…
This sounds like the sort of thing that could easily be automated using a five-line Bash (Ruby, Python, etc) script.
s3_website[0] is a very neat solution to this. It integrates automatically with Jekyll. A simple 'jekyll build && s3_website push' uploads all your changes to S3. I'm using it to power all my static sites. It'll even automatically invalidate your Cloudfront distributions, if you like.
Re: GitHub Pages with a custom root domain is slow
#44You shouldn't use a naked domain anyways, you'll never be able to grow a site on a naked domain properly for various reasons.
Would you like to expound on that at all?
Sure, here are a couple references that form my opinion:
https://devcenter.heroku.com/articles/apex-domains http://www.hyperarts.com/blog/www-vs-non-www-for-your-canoni...
No doubt there's ways around any problem with a naked domain, but why work so hard on something so trivial? No user has ever turned away from a website because it hadd "www." in front. That said, your naked domain surely needs to redirect to your "www." address if you set it up this way.
Re: GitHub Pages with a custom root domain is slow
#45Hi, Kyle with Neocities here. We support custom domains for sites too!
We use an A record right now for root domains because DNS does not support root domain CNAMEs, and as a consequence have very similar problems.
The only practical way to deal with the problem is to redirect root visitors to www. If you go to google.com, you will notice that they do the same thing and redirect to www from a proxy somewhere. Our next implementation will probably do the same.
Re: GitHub Pages with a custom root domain is slow
#46a better solution than doing DNS trickery is just doing proxying, but this requires some other machine to serve as the proxy. i serve my github pages blog on multiple domains, as described here:
http://igor.moomers.org/github-pages:-proxying-and-redirects...
Re: GitHub Pages with a custom root domain is slow
#47If you’re having trouble with a root domain on Github pages you may want to check out the Hosting product we (Firebase) just announced. It handles naked domains by having your root A record point to an Anycast IP that serves content from a global CDN. It’s lightning fast. We also support SSL (full SSL, not just SNI) and do the cert provisioning automatically for you.
Check it out: https://www.firebase.com/blog/2014-05-13-introducing-firebas...
Re: GitHub Pages with a custom root domain is slow
#48You may defer the DNS to CloudFlare. See the following for specific setup: http://davidensinger.com/2014/04/transferring-the-dns-from-n...
Re: GitHub Pages with a custom root domain is slow
#49I don't believe the lose. On a GitHub page are programming specific solutions for a problem a developer has. When somebody search for a problem or find a link to a GitHub Project, he/she will visit the page. All others don't have an urgent problem to solve, so you loose only users, that not need your solution. Can live with it. ;-)
That's what I thought too, although as far as I can tell it's possible to host any content on github pages. I suspect the majority of it is programming projects though, and programmers are not going to give up that easily.
Thats what i mean, if i want an information i try to get it and not give up because a server take 5 seconds "the first time".
Common Enduser surfin the web are an other species, but what should they seek on a github page ?
Re: GitHub Pages with a custom root domain is slow
#50Earlier quoted context omitted.
Yes. Numerous reputable entities have published reports demonstrating that users notice quite a lot. Amazon claims that every 100ms costs them 1% of revenue. Google claims 500ms costs them 20% of traffic. 5 seconds is a fucking eternity, and anything you expose to users on the web with such horrible performance will suffer greatly because of if. One exception may be banks. Users are more forgiving of latency as their…
I guess I find this plausible if we're talking about n ms multiplied by the number of resources loaded, and your page doesn't render progressively. If we're talking about total load time, I don't see why you'd even bother clicking a link if you weren't prepared to wait a few seconds for it to load. Edit: in the case of Google and Amazon, I can believe that being slow will cause users to defect to other services. I do…
Look at page speed vs. bounce rate in Google Analytics for any well-trafficked site. People are frequently casually clicking around, and the faster you have content up on the screen the more casual users will engage.
By analogy, to get into a different mindset, think about channel-surfing on the TV. If other channels show a picture in 0.2s, and as you flip around there's a channel that takes 0.8s to show a picture, are you more or less likely to surf past the slow channel?