3 ms·
Here's the actual TLDR from the article: * Dedicated hardware server—no shared hosting * Gigabit uplink to handle burst traffic * Varnish cache with lot
by CharlesW 9y ago
Here's the actual TLDR from the article:
* Dedicated hardware server—no shared hosting
* Gigabit uplink to handle burst traffic
* Varnish cache with lots of RAM
* Plugin-light WordPress installation
* Off-box stats via WordPress/Jetpack
* Cloudflare as a CDN
* No heavy dependencies (i.e., ad networks)
- js2 9y agoAnd really "Cloudflare as a CDN" was the most important. It absorbed almost all of the traffic: Between August 22 and August 30, Cloudflare served over five terabytes of cached Space City Weather content via Cloudflare’s CDN. Only about 145GB worth of requests had to be served by the Space City Weather Web server itself. [...] Looking at raw requests instead of bytes, Cloudflare handled about 88 percent of those, too, with only about 12 percent of requests passed back up the chain to the origin server. The origin server ended up seeing peaks of 50 RPS, most of that was absorbed by Varnish. I guess 50 RPS is a lot for WordPress, though I'm surprised given the origin server is a decent box: The server has a quad-core Xeon E3-1230 CPU, 16GB of RAM, and mirrored R1 SSDs.