So, what would a non-userspace solution look like? An HTTP keepalive + pipelinin... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		derefr on Oct 24, 2017 \| parent \| context \| favorite \| on: Why does one Nginx worker take all the load? So, what would a non-userspace solution look like? An HTTP keepalive + pipelining + HTTP2 implementation in the kernel that forwards the demuxed messages as separate packets onto a specially-typed socket, such that a prefork daemon can accept(2) individual HTTP request packets?

tyingq on Oct 24, 2017 [–]

There are a few problems outlined in the article. I was referring to this one:

"epoll() seem to have LIFO behavior which can result in uneven load balancing across workers (in case of accept()ing from a shared socket)"

Which is unrelated to keepalives and pipelining and best addressed in the kernel.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact