News for hackers. Stuff that matters.

A comment on How much memory do you need in 2024 to run 1M concurrent tasks?. Parent comment

Re:How much memory do you need in 2024 to run 1M concurrent ... by hamandcheese on Friday November 29, 2024 @02:11AM (#42271622)
> But you wouldn't call a million tasks with `Promise.all` in Node, right? That's just not a thing that one does.

But neither would you wait on a waitgroup of size 1 million in Go... right?

[ Parent | on HN ]
Re:How much memory do you need in 2024 to run 1M concurrent ... by ricardobeat on Friday November 29, 2024 @03:03AM (#42271917)
You could, and the tasks would run concurrently. Node is single threaded so unless you used one of the I/O calls backed by a thread pool, they would all execute sequentially .
[ Parent | on HN ]
Re:How much memory do you need in 2024 to run 1M concurrent ... by rtpg on Friday November 29, 2024 @02:38AM (#42271751)
yeah, right? I mean I don't have a dog in this race, just wished we could get into "normal" repros without having to wonder if some magic is kicking in
[ Parent | on HN ]
Re:How much memory do you need in 2024 to run 1M concurrent ... by rfoo on Friday November 29, 2024 @04:49AM (#42272633)
For a goroutine doing nothing, no.

But if I have 1 million tasks which spent 10% of their time on CPU-bound codes, intermixed with other IO-bound codes, and I just want throughput and I'm too lazy to use a proper task queue, then why not?

[ Parent | on HN ]