In previous post I described how we use Ansible in production environments for much faster deployments than coping with defaults. In this blog post, I will explain another one (simplified version) way to deal with incremental changes.
I was always interested in receive (RX) side when handling the packets (dunno why), but when you dig into the congestion avoidance situations you MUST pay more attention to sending side (TX).
One month ago I attended SRECon17 Europe in Dublin. You can read my humble notes about it if you want, but it’s not about that today.
As every last three years in a row, I attended SRECon in Europe. I can literally say this year was totally broken comparing with former conferences. I think it’s because I had much higher expectations from this conference. The first shot in 2014 was more than awesome, but year to year it’s getting worse. Almost all talks from Google were like a summary of every chapter in SRE book. We just skipped all the rest of the talks sourced by Google.
Almost every ISP responds unfortunately, they still cannot handle flowspec standard. It’s nearly 2018, almost every BGP-aware daemon software is able to send/receive flowspec. Those who don’t know what flowspec is:
Already 15 years passed when I played QuakeWorld and I feel too much nostalgic remembering those days. QuakeWorld (aka. Quake1) was released in 1996. It celebrates 21 this year and I tried to go back to 2002-2008 (it was the time I played QW quite professional). I must say, that well-known players such like Milton, Locktar are still on the track.
Nginx has two cool features to limit bandwidth for responses: