4 ms·
> I wish we could get back to working on getting FASTER cores rather than more of them. Some tasks just don't multi-thread. Out of curiosity, are you working o
by dahart 8y ago
> I wish we could get back to working on getting FASTER cores rather than more of them. Some tasks just don't multi-thread.
Out of curiosity, are you working on tasks that don't parallelize? There are some for sure, but maybe more that do parallelize, just not trivially or easily? It seems like some people have wanted faster CPUs rather than more parallelism for as long as I can remember... decades. I'm wondering out loud if your wish has ever not been true.
I suspect we're stuck with getting more cores until there's a new fundamental breakthrough in physics. We're hitting the wall with CPU speeds, which is why GPUs have been seeing all the growth recently.
So I just went looking and found a CS term for hard to parallelize I hadn't heard before: P-complete. https://en.wikipedia.org/wiki/P-complete https://en.wikipedia.org/wiki/P-complete Are you working on stuff related to or dependent on any of these examples?
- deepnotderp 8y agoI'm pretty sure OoO execution (which is how single threaded execution is improved in modern CPU cores) won't help with P- complete problems.
- DSingularity 8y agoNo not really. One of the biggest attractions of OoO is that it helps you find parallelism at the instruction level. So OoO as an architectural technique is one of the most helpful to problems hard to parallelize. The problem is there is a limited window of instructions where it can be applied. Trying to make one massive processor to find huge amounts of instruction level parallelism is just too hard.
- kingosticks 8y agoRecently on here[0], Arm claimed for every 7% extra resources they put towards increasing the RoB they got 1% performance. Past a certain point it's not worth it. That was their justification for having half the window of rival Samsung chips. [0] https://www.anandtech.com/show/12785/arm-cortex-a76-cpu-unveiled-7nm-powerhouse https://www.anandtech.com/show/12785/arm-cortex-a76-cpu-unve...
- deepnotderp 8y agoYes, but if there's mathematically zero parallelism then OoO can't really help that much.
- toiletfuneral 8y agoOpenSCAD could use some help https://github.com/openscad/openscad/issues/391 https://github.com/openscad/openscad/issues/391
- merinowool 8y agoAudio production. It is difficult if not impossible to parallelise one channel workload as each plugin depends on results of previous one.
- majewsky 8y agoIf the plugins are chained together in a pipeline, that's actually trivial to parallelize: Each plugin runs on its own core/hyperthread, with small ring buffers between them to pass data along the pipeline.
- merinowool 8y agoBut to process one plugin it still takes x amount of time and once cumulative x is longer than time of the audio buffer you'll get drop outs. That's why single core performance is the most important factor.
- majewsky 8y agoAh, you mean realtime? Yeah, then your concerns are right.
- Dylan16807 8y agoWhat kind of workloads require more than ten thousand instructions per sample?
- merinowool 8y agoSplice type of synthesizer emulations, variants of convolution, physical modelling, filtering, oversampling and so on...
- Dylan16807 8y agoSynth emulation sounds like it can take a fractional-millisecond hit to run buffered on a different core. "variants of convolution" is hopelessly vague. Physical modeling can't be parallelized? Filtering I'm not an expert on but that's exactly where I'd expect a few instructions to go very far. Oversampling I already took into account when saying "ten thousand". This is not to say that your problems aren't real. But I'm skeptical a concerted effort was ever made to go multi-core here. What's an acceptable level of total latency, so I can understand better?