How JavaScript works: Event loop and the rise of Async programming

Re:How JavaScript works: Event loop and the rise of Async pr... by api on Saturday October 14, 2017 @01:51PM (#15473290)

Anyone know if this is better in Alpine Linux with musl libc and smaller stacks?

[ Parent | on HN ]

Re:How JavaScript works: Event loop and the rise of Async pr... by dozzie on Saturday October 14, 2017 @02:07PM (#15473364)

It's not really up to a distribution to lessen this cost. Large part of it is what task descriptor in the kernel takes.

Also, if nothing else, you'll run out of PID numbers, as they're usually still 16 bits, even today, though there was a kernel compilation option to change that, from what I remember.

[ Parent | on HN ]

Re:How JavaScript works: Event loop and the rise of Async pr... by bluetech on Sunday October 15, 2017 @05:16AM (#15476465)

It can be changed at runtime. From proc(5), system wide limits:

/proc/sys/kernel/pid_max

> PID_MAX_LIMIT, approximately 4 million

/proc/sys/kernel/threads-max

> FUTEX_TID_MASK (0x3fffffff), [approximately 1 billion]

For per-process limit, increase RLIMIT_NPROC.

[ Parent | on HN ]

Re:How JavaScript works: Event loop and the rise of Async pr... by pcwalton on Sunday October 15, 2017 @01:05PM (#15477984)

> Large part of it is what task descriptor in the kernel takes.

4K for kernel stacks, only 2K with future work. That's really not much space at all if you're doing anything interesting with those threads.

> Also, if nothing else, you'll run out of PID numbers, as they're usually still 16 bits, even today

Not for a very long time.

[ Parent | on HN ]