Conversation

saleem

⍼

@saleemrash1d

Oct 6, 2021

things are heating up in the computers fandom

at this rate, prepare for apocalypse by friday

it's happening

read image description

ALT

screenshot of me running "curl https://www.tiktok.com" and it printing "The connection cannot be served because Server.Concurrency limit exceeded"

read image description

ALT

ahem

fasthttp/server.go at v1.30.0 · valyala/fasthttp

Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http - fasthttp/server.go at v1.30.0 · valyala/fasthttp

This Tweet was deleted by the Tweet author. Learn more

Replying to

and

The number of connections is inherently limited by the memory required for each. There's a reason for these connections limits in pretty much any serious server software including web servers like nginx. Dropping new connections is better than everything getting screwed up.

Replying to

and

It has to be configured based on the memory available to the server and the memory required for each connection. Go servers use a goroutine for each connection or request which is quite memory hungry compared to a highly optimized approach. Limit has to be lower than nginx, etc.

11:21 PM · Oct 6, 2021Twitter Web App

Replying to

and

As an example: nginx.org/en/docs/ngx_co The alternative is that it maxes out the number of file descriptors or memory and starts having problems across the whole server including existing connections. Presumably TikTok does have it configured reasonably and is just overloaded.