This Week in Website Performance

This Week in Website PerformanceThis Week in Website Performance is a weekly feature of the blog. It summarizes recent articles about website performance. Why? Because your friends at care.

Web Performance: When millisecond resolution just isn’t enough

Author: Jatinder Mann.

The tool was just an idea 8 months ago. As of this week, this specification has been published as a Proposed Recommendation (PR) and is widely adopted in modern browsers.

Real-world CDN performance for Google DNS and OpenDNS users

Author: Sajal Kayan.

This is the third article of a three part series covering the impact of DNS choices on CDN performance. This covers many CDNs including Akamai, CDNetworks, fastfly, EdgeCast, FastFront and others. Comparisons were done in several global loactions. Real-world performance data is presented that demontrates this and gives good insight in how CDN performance for Google DNS and OpenDNS users compares against all users.

HTTP/2.0 is good news for CDNs and FEO

Author: Guy Podjarny.

Some people have been thinking that HTTP/2.0 will make FEO and CDN usage obsolete. Guy Podjarny has written about how HTTP/2.0 does and does not affect FEO and CDN in this well-rounded article.

Caching in theory and practice

Author: Pavel Pancheckha.

The Least Recently Used (LRU) algorithm is compared to other simple cache types: Most Recently Used (MRU), and Least Frequently Used (LFU). This informative article shows why LRU is the choice for DropBox, and provides plenty of background information to help you decide what is best in your situation.

How to Triple Throughput and Improve Application Performance Through End-to-End Testing

Author: Andreas Grabner.

End-to-end testing can show where the problems are, and where to focus energy in correcting the performance. This article-cum-case study illuminates how end-to-end testing can discover a poorly deployed server. Another core point is the value of looking at more than averages as the biggest problems are found in the outliers.

Simpler, Cheaper, Faster: Playtomic’s Move From .NET To Node And Heroku

Author: Ben Lowry.

Playtomics is a game analytics service which migrated from .NET to NodeJS for significant server savings. Read about how they did it and what the performance is like in this detailed article.

Just over 20,000,000 people hit my API yesterday 700,749,252 times, playing the ~8,000 games my analytics platform is integrated in for a bit under 600 years in total play time. That’s just yesterday. There are lots of different bottlenecks waiting for people operating at scale. Heroku and NodeJS, for my use case, eventually alleviated a whole bunch of them very cheaply.