News for hackers. Stuff that matters.

A comment on Wangle – an asynchronous C++ networking and RPC library. Parent comment

Re:Wangle – an asynchronous C++ networking and RPC library by otabdeveloper on Wednesday April 20, 2016 @03:25PM (#11537037)
> Does that mean that one can use system threads as frivolously as goroutines (e.g. spawning new thread for each incoming request)?

Yes. In fact, under Linux oftentimes spawning a thread and then running a system call can be faster than just running a system call.

> Conventional C++ wisdom advices against it.

With 32 bit CPU's you might run out of virtual memory quickly, since each thread allocates virtual memory for its stack.

With 64 bit CPU's there are no issues. (Also never forget that virtual memory isn't real memory, it's just a page counter.)

[ Parent | on HN ]
Re:Wangle – an asynchronous C++ networking and RPC library by pcwalton on Wednesday April 20, 2016 @04:14PM (#11537380)
> Yes. In fact, under Linux oftentimes spawning a thread and then running a system call can be faster than just running a system call.

Interesting, do you have any further info (references, cites) on this?

[ Parent | on HN ]
Re:Wangle – an asynchronous C++ networking and RPC library by scott_s on Wednesday April 20, 2016 @05:04PM (#11537750)
Sign me up for wanting more info as well. I'm curious how that could work out, since spawning a thread is a system call.
[ Parent | on HN ]