core-async

jumar 2019-10-10T07:27:50.001300Z

I'd add to the yesterday's discussion that it might not be the best idea to use a/thread but instead use your own thread pool of limited size. So you don't end up spawning one thread for each go block/process.

2019-10-10T16:21:55.001500Z

it depends

2019-10-10T16:24:14.003500Z

(that was wildly inaccurate)

2019-10-10T16:24:46.003800Z

but I am going to stand by it depends

2019-10-10T16:43:18.003900Z

threads are cheap, it's context-switches that are expensive, it's more important to make sure significant work happens in the thread (so the amortized cost of the context switch is lower) in most cases

2019-10-10T16:43:35.004100Z

but as said elsewhere, it depends

jumar 2019-10-10T20:04:24.004300Z

Sure, it depends. But you can create 10,000 go blocks easily but it's probably a bad idea to spawn a new thread immediately for each of them