News for hackers. Stuff that matters.

A comment on Multi-threading is always the wrong design (2023). Parent comment

Re:Multi-threading is always the wrong design (2023) by andy24 on Friday April 04, 2025 @01:59PM (#43585783)
Isn’t Nginx multithreaded rather than multiprocess? I’m not an expert in web stuff but it’s always felt intuitively that worker threads map nocely into typical web server workloads.

Also, any UI app should basically be multithreaded to prevent interface hiccups.

[ Parent | on HN ]
Re:Multi-threading is always the wrong design (2023) by packetlost on Friday April 04, 2025 @10:38PM (#43590158)
No, nginx uses a fixed number of worker processes and communicates primarily through explicit shared memory and message passing.

Threading works ok, but there's rarely much shared state so the fork and pipe / she model wins cleaner and more secure.

As for UIs: maybe! I'm sure it depends, but this isn't an area I know a ton about

[ Parent | on HN ]
Re:Multi-threading is always the wrong design (2023) by andy24 on Sunday April 06, 2025 @05:43AM (#43600199)
Interesting perspective, I’ve never been thinking about this problem in terms of whether workers need shared memory space. Thank you!
[ Parent | on HN ]