4 ms·
There is nothing hard about this. You either have a "problem" that can take advantage of multiple cores or sequential reading from memory or you don't. The only
by h1290799 11y ago
There is nothing hard about this. You either have a "problem" that can take advantage of multiple cores or sequential reading from memory or you don't. The only way to avoid this is to change the "problem"
- MichaelGG 11y agoMany times you'll have code that doesn't take advantage of multiple chores and sequential memory, but could. Redesigning it is what's hard.