« ELECTRIBE Wave v2: New Features and Basic Tutorial | App News | PolyHarp by Henry Lowengard »

New Web Server is Live!

The site swapped to entirely new servers last night! There were some issues, but I've been able to fix them as I find them. Big thanks to pantsofdeath for being my beta tester and alerting me to a big bug. Most people will hit errors and not report them. I'm begging you: Please report any bugs you find! Don't assume I know about it. As of right now I am aware of no bugs on the site. Seriously, please tell me if you find one!

Throughout its life discchord has resided on several hosting platforms. Initially it was just a simple Squarespace v5 blog. When I decided to write my own CMS this meant I had to get proper hosting, but I was pretty spoiled by Squarespace's reliability. I thought I'd find similar reliability on the mighty Amazon Web Services (AWS) platform, especially for the price. I was mistaken. I got a very good deal on the web hosting from PythonAnywhere (a Managed AWS web host), but the database hosting from mLab (a Managed AWS database host) that went with it was quite expensive and not at all reliable. This site has a very large database of comments, articles, apps. It's not quite "Big Data" but it's hefty, and growing.

I'm just about to launch AppKaiju, my AppShopper killer. During its development I needed an even larger database that would include all of the apps on the App Store. mLab was going to charge me a kidney for a database of that size, so I decided to set out on my own. This turns out to have been a great move. I migrated discchord's database on to the new server cluster, along with AppKaiju's insane database size, and still have plenty of space left to grow. That was 7 months ago. It has been much more reliable than mLab/AWS!

For the last few weeks I've noticed some performance issues on the discchord webserver in the morning while I'm trying to write articles. This is simply you guys coming here because you know the schedule and you're coming to see what's new. There are a lot of you, so that was beginning to overwhelm the PythonAnywhere (AWS) server. I had two options: ask you all to stop coming to the site because you're slowing it down, or upgrade the server. Yesterday I went with the latter.

And the new site is so fast! Holy shit! Go click around and see how fast it loads! This new server is running a faster processor from the one I had at PythonAnywhere, and it is in the same room as the DB cluster. I'm so excited! discchord is my baby. Right now my baby is very healthy and I'm 100% responsible for its care. No more managed hosting or middlemen. I am solely responsible for maintaining all the servers that run the site. This is incredible to me, because 4 years ago I couldn't do any of this. I couldn't write backend, I knew nothing about databases, and I definitely wouldn't know the first thing about running a cluster of Linux servers.

Now I'm a full-fledged DevOp. As with music making, it was simply a matter of dedicating the time to practice.

Reader Comments 22

Congrats on move, always a PITA. Why no HTTP/2?
November 28, 2018  | person huphtur
Thank you!
November 28, 2018  | person The other Brian
On November 28, 2018 - @huphtur said:
Congrats on move, always a PITA. Why no HTTP/2?
From my understanding, and this is somewhat limited, the site's architecture wouldn't benefit from it. If I used something like React this would be more useful. The front-end here is Angular 1 which was entirely unlike any of the other JS frameworks today (including Angular 2+). So I still have the front-back paradigm with API requests, but only for small things like populating the app links.

So in the HTML your browser receives a link to Animoog looks like this (I swapped the < and > with [ and ] because the comments here won't allow HTML... even from me!):
[itunes app="id471638724"][/itunes]
Angular then queries my API for all the details like name and icon, then spits out this:

[div class="iTunesLink layout-row" layout="row" style=""][div class="iTunesIcon layout-column" layout="column"][a href="https://itunes.apple.com/app/id471638724?mt=8&uo=8&at=11l4Kv" target="_blank">https://itunes.apple.com/app/id471638724?mt=8&uo=8&at=11l4Kv" sl-processed="1"][img class="iOSAppIcon" src="https://is5-ssl.mzstatic.com/image/thumb/Purple115/v4/10/46/19/10461953-79c0-ba82-3ec4-10d14acde10c/source/100x100bb.jpg"][/a][/div][div class="iTunesLinkBody layout-column" layout="column"][div layout="row" class="iTunesLinkName layout-row"][a href="https://itunes.apple.com/app/id471638724?mt=8&uo=8&at=11l4Kv" target="_blank">https://itunes.apple.com/app/id471638724?mt=8&uo=8&at=11l4Kv" sl-processed="1" data-skimlinks-orig-link=""][h3 class="ng-binding"]Animoog [span class="appPrice ng-binding"]$29.99[/span] [/h3][/a][/div][div layout="row" class="iTunesLinkDevices layout-row"][span class="appDevices ng-binding"]iPad[/span][span class="appBouncer ng-binding"][/span][/div][div layout="row" class="iTunesLinkRatingWrapper layout-row"][a href="/appDB/id471638724" title="Reader Rating" class="ng-binding" sl-processed="1"][md-icon class="iTunesLinkRatingIcon material-icons"]thumbs_up_down[/md-icon]96%[/a][a href="/appDB/id471638724#comments" title="Comments" class="ng-binding" sl-processed="1"][md-icon style="padding-left: 0.25em;" class="iTunesLinkRatingIcon material-icons"]comment[/md-icon]1[/a][a href="/presets/id471638724" title="Presets" class="ng-binding" sl-processed="1"][md-icon class="iTunesLinkRatingIcon material-icons"]file_download[/md-icon]1[/a][/div][/div][/div]

On many articles I have to manually put in the iTunes links, so it is nice to just be able to have a small thing to plug in there to generate that big block of code in Angular.

But that's about all Angular does. Small API tricks like that. Most of the data you get from a request here is in the big chunk variety, like traditional websites of the past. The front-end stuff that would benefit from the HTTP/2 is very minimal in my design.

I will definitely explore it at some point, and try to benchmark it for myself, but I'm in no rush.
Hi Tim,
Congratulations and many thanks for your great work!
Here is a bug that I have been witnessing for quite some time: Firefox iOS in private mode is nearly always displaying your “error banner” (the one aimed at people using ad blockers) for at least one ad, but never all of them. I couldn’t detect any pattern in this behaviour, but it is definitely reproducible. So maybe you might want to have a look at this at some time? After all, I am NOT using an ad blocker, so this message seems kind of pointless to me ;-)
November 28, 2018  | person_outline Granthafen
On November 28, 2018 - @Granthafen said:
Hi Tim,
Congratulations and many thanks for your great work!
Here is a bug that I have been witnessing for quite some time: Firefox iOS in private mode is nearly always displaying your “error banner” (the one aimed at people using ad blockers) for at least one ad, but never all of them. I couldn’t detect any pattern in this behaviour, but it is definitely reproducible. So maybe you might want to have a look at this at some time? After all, I am NOT using an ad blocker, so this message seems kind of pointless to me ;-)

Thanks for letting me know! I'll test that out and see if I can figure out what's causing it. Does this happen in all of the ad positions, or just a specific spot?
Yes and no - if I remember correctly, this never happened to the ads on the right side, only the three slots on the top. But here it is totally random: when I just came to this page, only the right ad was affected; after a page reload all three slots are showing your banner now...
November 28, 2018  | person_outline Granthafen
Wow this is really weird. Firefox is blocking Google AdSense ads on all platforms (Windows, iOS, and Android in my tests). I looked into it, and this is by design. If you're in Private Mode, or have Do Not Track set, they just flat out block AdSense on the grounds that Google will track you when they load an ad. This isn't always true after GDPR. In fact it is never true for Europeans. discchord's code is supposed to be using the non-tracking version... or at least as non-tracking as Google allows.

This feels like the Mozilla team trying to give the finger to Google, which I can respect, but they're doing it in a hamfisted way that punishes everyone.
"World falls apart"

-> that is one cute cable nibbler though:)
November 29, 2018  | person_outline Spaced invader
On November 29, 2018 - @Spaced invader said:
"World falls apart"

-> that is one cute cable nibbler though:)

Thanks! He was humanely sourced on Fiverr from an amazing Filipino artist. She did 3 poses for me. This pose is the one most people (hopefully) won't see, because it is for server errors.
I don’t know if this is related to server errors, site bugs, or iOS being an asshole, but I couldn’t just tap on the “comments” link to get here. No matter how many times I tapped on it, the link changed color but did nothing else. I ended up using a 3D Touch “deep press” to force Safari to go to this page.

Also, after posting comments, I seem to have to go back three times, instead of two, to use Safari’s back function to get to the previous page. So many websites overtly break the back function of web browsers these days and I hadn’t bothered to report it as a site bug.

Frankly, I’ve always found this site hard to deal with on iPhone. The design doesn’t fit the scale of iPhone well at all (links are tin, and the layout is too wide; I’m constantly scrolling left and right to create comments, or just to read the tiny text). I assumed my trouble with tapping links was merely because I wasn’t zooming in far enough, but I’d also catch the link color changing, suggesting I hit the mark, yet I still had to hit it several more times or zoom the hell in.

Sorry to sound so negative; you asked for reports and for us to not presume you are aware of any problems we notice.
November 29, 2018  | person dysamoria
On November 29, 2018 - @dysamoria said:
Sorry to sound so negative; you asked for reports and for us to not presume you are aware of any problems we notice.

Yep, I literally asking for it! ;)

I'm not happy with the way the site performs on phones, but changing it is non-trivial. The right way to do mobile is designing "mobile first" and then building up from there. Essentially a redesign. That's not happening, so I've been trying to think of some other solutions. I've been thinking about it for years and have yet to hit on anything I like.

I'm not doing anything with the back button, so any problems there are unintentional. The links not working on first press also sounds weird. I think I know what might be causing that, because I've seen some similar behavior in my own tests. It is Angular's fault. Which is ironic... I opted for Angular as the front-end because Angular-Material was designed for mobile! All the buttons and everything are nice and big for mobile use, but I've seen some weirdness on links like you're describing.
Great work, Tim!! Persistence and perseverance pays off. Congratulations on the DevOp status!!! Keep it up.
November 29, 2018  | person BDBaker1958
I ended up going with hetzner in germany, they seem to be a nice balance between good price and a company that i trust.

Got my music projects name Cyp3.com , i been writing up the content on a notepad so I can focus on content rather than fidgeting with the site. Will probly use wordpress unless tim sugests somthing more secure.

My aim is the home / main site will be for my music project then a sub domain will be my side projects such as a blog about visuals and mobile production, work flow, touring, networking, interviews with people everyone is wondering about.... like for instance i might stalk intua like paparazzi!!!!!!!
November 30, 2018  | person_outline Ian
Tim I have many times wondered why you dont use your skills to do a series on setting up sites for our music projects. For instance Im completely confused, Im scared to even add wordpress to my server, Completely ignorant regarding even the basics in security..... im clueless, yet ive had a website before, so folks who have never touched it might benefit even more, perhaps your just tooooo busy, it sounds like your quite good at keeping your hands full! :)
November 30, 2018  | person_outline Ian
On November 30, 2018 - @Ian said:
I ended up going with hetzner in germany, they seem to be a nice balance between good price and a company that i trust.

Got my music projects name Cyp3.com , i been writing up the content on a notepad so I can focus on content rather than fidgeting with the site. Will probly use wordpress unless tim sugests somthing more secure.

My aim is the home / main site will be for my music project then a sub domain will be my side projects such as a blog about visuals and mobile production, work flow, touring, networking, interviews with people everyone is wondering about.... like for instance i might stalk intua like paparazzi!!!!!!!

Hetzner is great, Wordpress isn't. Wordpress itself is fine, but because of its popularity there are a lot of people trying to exploit it. My security logs are full of bots that just spend all day running around trying to hit known Wordpress exploits. New exploit vectors are being found monthly. Lately they've been targeting Wordpress plugins with some success. I'm not sure what else to recommend instead of Wordpress, but I think you'll be safer with literally anything else. If you didn't need a subdomain I'd actually encourage you to just use Squarespace. It's cheap and secure, but it is limited in what you can do.

On November 30, 2018 - @Ian said:
Tim I have many times wondered why you dont use your skills to do a series on setting up sites for our music projects. For instance Im completely confused, Im scared to even add wordpress to my server, Completely ignorant regarding even the basics in security..... im clueless, yet ive had a website before, so folks who have never touched it might benefit even more, perhaps your just tooooo busy, it sounds like your quite good at keeping your hands full! :)

That is a very prescient comment. I have been toying with the idea of doing something along those lines for a while, and in the last month or so decided I was definitely going to do exactly that. It probably won't happen until sometime next year, but it will be soon. After I get AppKaiju launched I need to do something for Gnubesoft.

http://gnubesoft.com/

Man that is a sweet banner I made for it. Now I just need to do the rest.
I understand the lack of motivation to redo the design. I set up a blog again for the first time in many years and tried to customize the design. I hate Wordpress, hate the themes, and HATE CSS with the fire of a million stars.

I spent a whole day fucking with tying to find a moderation point between desktop and mobile while customizing a theme. CSS S U C K S to an incredible degree. It is the absolute worst technology I’ve ever tried to learn. Even people who know it well recognize how horrible it is. By the end of my horror day of working on the design (and I’m talking MINOR changes here) I found a thread of people talking about how horrible CSS is. It sort of made me feel better. A little. I found this there:

https://1.bp.blogspot.com/-YNZS7oHbnbU/WPRMe8mVbuI/AAAAAAAAAgw/PyS6c96rQJMYHU0Mm1roWqghOAxlb1CtwCPcB/s1600/image1.PNG

Anyway, I’m glad my observations aren’t “just me” thingies :-)
December 01, 2018  | person dysamoria
thank you @dysamoria - that shit made me chuckle. CSS does suck, but it has kind of always sucked and flexbox has actually made things a LOT easier.

[One hour+ later. I got going and wrote a text wall. Sorry. Most of the following is completely unsolicited technical feedback and not bugs, but just consider it, um, "free consulting"? I am greatful for all you do Tim and more power to ya for building your own CMS!]

Ok, so I love your work and you are I think literally the *only* iOS Music resource that has the huevos to actually give negative reviews or be critical. Has Doug or Jakob ever actually /not/ liked something and expressed that? You keep it real son, and I love you for that.
Anyhoo....I'm an asshole who is also a Web dev (though primarily front end), but I have used and deployed to AWS. I'm really sorry I didn't know about your troubles until now. First, let me say that I am really happy your new host is much more to your liking, and it seems plenty snappy to me atm. Of course, the biggest issue with AWS is that it is a clusterf*ck [oh wait, this is discchord], a total clusterfuck of ~150 services, many of which overlap. Goddamn nightmare.
The thing is, AngularJS aside (dear God, who suggested that to you? Buy them an offbrand chinese hoverboard scooter or Galaxy Note 7 for Xmas) your site is a completely custom CMS, right? As such, I am heavily inclined to hold the mirror up to your code and system-layout before knocking AWS. God knows if they can run Expedia and AirBnB, they have the capability to handle this baby. The tip off to me is that, if in any way there were speed problems because of heavy traffic like you mention, either your DynamoDB, EC2 instances/containers, or ELB weren't configured correctly. There should be no concept of a single server being overwhelmed. At least not for more than the __[5-30?]secs it would take to spin up a new Docker container. So, no offense, but I doubt it was "on their end". I'm not here to defend some corporate behemoth nor shit on you, but there are lots of little gotchas with AWS where things will work fine, even in production, but don't work well with heavy traffic - Something like...if you were using S3 buckets or NFS for your code, you'd be shooting yourself in the foot right there... But whatever, the past is past and over and done with so fuck those guys amiright.

On to the here and now - I'm a front end guy and to me, the single most "annoying" and fixable thing about the site is the way that the ads as well as the youtube frames load in. The painting of the ads is always very delayed. I get that your thing is having a combo of custom ads of your own and external content coming in from google/AdChoice, but they just don't load at the same time and that is the first thing under the header image so you can't help but notice it. The good is that you do have the boxes for them, so it's not that thing where suddenly the whole page jumps as content loads in, but it's still a jarring UX. Any way to pre-cache the ads? With the youtube frames, obv you can't control what they are going to do and since almost all of your pages have a set of youtube embeds, it is a tough situation. Those embeds are the lion's share of the memory footprint of your site and the cause of weird jank when you scroll quickly up and down. My only thought there is to do a trick where you first put a total dummy blank image in (black rectangle, white circle in the center, black triangle inside of that. Whole thing can be done in CSS), then, replace it with the youtube thumbnail\poster image (which can itself can actually be an anchor link to) when that loads in, and only /then/ load in the embedded youtube component. I did a run of Lighthouse (the audit panel in chrome devtools), and the first meaningful paint came after 4seconds, and while the spacing was there, it only had 2 out of the 3 top ads and a big blank space for where the youtube embed was going to load in in the first post. Mind you that is on my home MacBook at full Wifi. Change it to say, 3G and it becomes something like 30seconds to interactive!

Oh, wait, I did find a bug, if you would even call it that. On desktop, on the right side of #canvasWrapper there is a 1px border that goes the full height of the page. It does add cohesion to the top half, where you have content (more on that in a bit) but what ends up happening is that eventually the right side is just an empty space with a line. Since you tend to have a kind of long vertical layout, I would normally try to suggest some way of having the last element on the sidebar be set with position:sticky so it floats along with the UI, but the way you have things right now, with the ad box below the comment box, it gets trickier.

Random unsolicited ideas because I'm a douchnozzle.
- change the top/bottom overscroll areas from solid black to having the same sort of grey to black gradient as div#billboard. (purely aesthetic)
- The body background loaded from a url call to /storage/site2014-2x2bg.jpg as a background texture, to me, seems almost indistinguishable from a dark/flat shade of grey. Repeating backgrounds are swell, and it's nice to add texture, but something only 4px wide is to me so subtle that performance wise, it's just adding unnecessary load work on the browser's paint rendering because the engine has to figure out how to redraw the same 4px a babillion (technical term) times.
- The nit pickiest thing that bugs me -> #sidebarWrapper is a fixed 204px, and you've got it futzed so that .menusection>.menu2014's [li]s (damn no \< \> brackets!) look like they are that wide as well. Ok. But all of the ad images in #WeDontNeedNoStinkingBadges are 200px underneath a 204px element. And /then/ .recentcomments below that comes out at 199 px. Devil is in the details, so call me Satan. Wouldn't hurt all of them to be the same width.

I don't know "how to" for much of the following but if you're the back-end ops guy...
1. You *have to* get down with http2. It makes[/will make] *everything* faster. Period. Just like we've recently hit httpS as the new normal, http2 will be.
2. You *ought to* get down with gzip-ing a bunch of the site's assets.
3. You *definitely* should raise the cache TTL on all of the Angular bs. That shit is taking up almost 9 seconds of network time! Multiple MB. Right now the Angular files' cache expires after only 12hrs and that library ain't changing that fast on ya...
All three of the above will reduce your network costs if nothing else.
4. Long term, peep a bit about how GraphQL queries work. It would be a bonus for the kind of content structure this site needs, but that is a long term thought. For my money, just as SOAP replaced REST in many if not all situations, GraphQL is going to overtake REST in most situations.

Design for what your analytics tells you. In your case say, I wouldn't be too worried about Google AMP because, while it would generally help for this sort of content marketing, you are obviously (I'd think?) dealing almost exclusively with iOS and OSX devices. I don't know the breakdown of ppl that visit the site on Mobile vs Desktop (vs Ipad), but I know I pretty much exclusively read it on my iPad. Good news - no need to worry about any legacy IE bs. Bad news - you have to worry about all the Safari bs.

Oh, and your SEO is taking a hit simply because you don't have "\
Holy shit, I've ended up writing a crazy amount. Ooops. Imma just cut myself off. Honestly, I haven't even reloaded the site in "Mobile" mode but we can save that for another time... Sorry.

tldr; I don't see any bugs, but as a ocd nerd there is plenty of relatively easy stuff that could be done to improve it.
December 01, 2018  | person b0bert0
To the last post , the first thing that came to mind here is, web devs do the same thing producers do, getting lost on details no one in thier right mind or ( or left) would ever notice or care about. That said, i never noticed the ads loading at seperate times, but i have noticed tims preference for his own ads vs the industry shit, and those custom ads are the only way it should be,not based on invasive cokkie echo chambers, but based upon tim and his site and his view of his market. Hes fortunate or in tune enough to run a site where his readers are invested in the company's hes advertising which is fucking rare. I just wanted to say something about that, i find it really authentic and non invasive, I actually look at this sites ads, and i have a complete blindness to adverts anywhere else .
December 01, 2018  | person_outline Ian
On December 01, 2018 - @dysamoria said:
I understand the lack of motivation to redo the design. I set up a blog again for the first time in many years and tried to customize the design. I hate Wordpress, hate the themes, and HATE CSS with the fire of a million stars.
It gets easier... but only after burning in the heart of those stars for several years. CSS is wildly inconsistent in a lot of the naming conventions. You could have two properties that do basically the same thing, but with slightly different keywords. Center vs Middle for example. CSS gets easier when you learn all of those quirks. But yeah, I hate it. I hate it deeply. It can still take up a whole afternoon for me to style a page when I try to get fancy.
Yeah i had a feeling wordpress is too popular for its own good. On an unmanaged server that would be an endless job. In the end, if my time is worth anything to me your recomending squarespace is probly words of wisdom. i will probly wish i followed it but yeah, the subdomains, thats where all the fun is!!!!!!!!
I totally look forward to your future projects! You have a whole lotta skills that transfer toward the music industry, soooooo many people here who have been with you for some years now, they are probly ready to start building platforms and online presence for thier projects that were born in our little community. I see quite a few people here and on audiobus who are right there and ready but probly just as confused and burdoned with questions as i am..... building a secure solid functional platform is probly as important as workflow and synths ever were... just some pointers and tips, perhaps some q&a type call ins, interviews, faqs, lists...
December 01, 2018  | person_outline Ian
@b0bert0: Thanks for taking the time to write all of that.

re AWS: The real problem for me was the servers constantly going down. This was especially messy on the database servers, because with mLab I only had 2 servers in the replica set. This lead to a lot of conflicts that I'd have to manually deal with. The webserver from PythonAnywhere was basically AWS's last generation, so it may be unfair for me to judge the performance there... but it was slower than this new whiz bang one!

re CSS: The things you pointed out with the odd widths are legacy issues. When I redesigned the site, I wanted to make sure it didn't change too dramatically from the SquareSpace version because the majority of my readers are old men, and old men do not like change.

I reused a lot of the CSS to make sure it was styled in the way people expect. Some of that code is over 7 years old. I don't even remember how or why the widths were different. I suspect I was trying to space them evenly when centered. The sidebar itself has changed widths slightly over the years. Have you read any of the Zones of Thought Sci-Fi books? The first one is amazing, the second is great, and the third is a fucking train wreck. I highly recommend reading the first two. In the second there are all of these fun terms like Programmer-At-Arms and, "programmer archaeologists." The code base for discchord is now so big and so old I basically have to fulfill that role. I do a good job of commenting my code, but even still I'm often left wondering, "What did this ancient code structure do? And why did the Mesopotamians worship it as an idol god?"

I did try using a flat background, but I look at the site more than anyone else and the textured background looks much better on my monitor!

I'll take a second look at HTTP/2. I spent some time this morning brushing up on GraphQL. I greatly look forward to the time when Apple and Google start to use it... but it is a Facebook thing so that seems somewhat unlikely. This is great for querying public APIs, but not relevant to the way my front and back-end communicate. They're much shorter and specific, so they are less like Queries and more Gimmies. My front-end says: "Gimmie the data on this app." And my back-end knows which information is relevant so it is designed to only return the that relevant data.

I've been meaning to look into gzip and really should look to see how I can use that.


You *definitely* should raise the cache TTL on all of the Angular bs. That shit is taking up almost 9 seconds of network time! Multiple MB. Right now the Angular files' cache expires after only 12hrs and that library ain't changing that fast on ya...
Oh dude, you are so right. I should have done that from the get go. It was a huge oversight on my part! I'll get that fixed as soon as I figure out how to do it with gunicorn and nginx. My first attempt failed...

I'm also going to explore getting rid of the black line on the right when it exceeds the recent comments section. Thanks for pointing that out! And seriously thanks for all of this! I can tell you spent a lot of time on it, and I greatly appreciate the free consulting!
I got the caching working now on all of the static files. Thanks again for suggesting that. It was one of those things I thought about when I was launching things, but it got pushed out of the way by more immediate concerns... and then pushed out of mind entirely. Next up is figuring out compressed transfers for those bloated JS files! I've always hated how big Angular is. For AppKaiju I decided to write my own jQuery-based front-end with just the things I need. As in the case of writing my own CMS, the benefits to an entirely custom front-end are huge. It also takes a fucking age to write, but my front-end comes out to 59KB versus Angular's 10MB!

I looked deeper into HTTP/2. This is definitely the future of the web, but everything I've seen confirmed my initial suspicion that the site would not benefit greatly from it. The parts that would, like the YouTube videos and other big external resources, are already using HTTP/2 from those providing servers. Or in some cases SPDY. Aside from my JS, CSS, and the site banner, most of the things you download when you visit here are coming from external sources. All of the app icons and screenshots come from Apple's CDN.

There is a big gotcha to HTTP/2 that makes me hesitant to implement it. The initial handshake is much longer than HTTPS. So all of the bits that you would hope to download faster, will all start later. Since it allows for simultaneous transfers it might make up for that and more. This is a delicate balance that will require a lot of benchmarking to determine if it is a help or a hindrance.
comment

  Post a New Comment

You are not currently logged in. Would you like to login or register?
Enter your information below to add a new comment anonymously.

I'm not a racist, but...
Usernames need to be at least 2 characters!
I'm not a racist, but...
Please don't use weird characters in usernames!
{[ Ctrl.useravailable[Ctrl.userselector] ]}
{[ Ctrl.useravailabletext[Ctrl.userselector] ]}
Wow, that's a short email address!

Comment:

Do not use HTML in your comments. Tags: [b] Bold Text [/b] [i] Italic Text [/i]
Links will be generated if you include http:// or https:// at the beginning of a URL.
Submit