3 ms·
> is switching address spaces at the same time going to kill you? The answer is "yes". I won't stop you, if you want to make React even slower, be my guest. I
by otabdeveloper4 3y ago
> is switching address spaces at the same time going to kill you?
The answer is "yes".
I won't stop you, if you want to make React even slower, be my guest. I want off this ride.
- quotemstr 3y ago> The answer is "yes". And if you have one per core anyway so nothing "switches"? Computers aren't single-core 80486es anymore. We have highly parallel machines nowadays and old intuition about what's expensive and what's cheap decays by the year.
- JackSlateur 3y agoYou know that process A (the caller) is currently running. You assume that process B (the callee) is running in another core on the same NUMA nodes.
- otabdeveloper4 3y agoSorry, not dedicating a whole CPU core for your shitty React app.
- josephg 3y agoI only have 16 cores. Linux, windows and macOS already load about 50+ processes at startup. If we moved shared libraries into their own processes, we’d be talking hundreds or thousands of processes running all the time. They don’t get a core each. But, if you’re interested in this architecture, smalltalk did something similar. Fire up a smalltalk vm and play around!