4 ms·
How would one write code for such a monster?
by milesf 10y ago
How would one write code for such a monster?
- jcranmer 10y agoCharm++?
- 59nadir 10y agoUsing erlang.
- colanderman 10y agoErlang is a great way to write code that's distributed across a network and which is generally I/O bound. It's a terrible way to usefully use compute on manycore systems.
- reacweb 10y agomake -j200000 --load-average=200000
- colanderman 10y agoGenerally you need to make the most of such tiny cores. This usually means dedicating any given core to a specific task, whose work of pulls off of a queue in batches. This way stuff tends to stay in each processor's local cache and you can minimize synchronization. If instead you make every core do everything, stuff falls out of cache and you're forced to synchronize across cores and performance suffers.