2 ms·
Cache-oblivious code is a lot more successful in the real world, because systems change over time. Hardwiring code to rely on a rigidly predefined amount of ca
by zozbot234 4y ago
Cache-oblivious code is a lot more successful in the real world, because systems change over time. Hardwiring code to rely on a rigidly predefined amount of cache is the worst kind of premature optimization.
- binarycrusader 4y agoIsn’t “a lot more successful” is only true more generally? Many developers have fixed platform targets for the life of a product (e.g., consoles, embedded, microarch). So I’d agree in general but hesitate to say “a lot more successful”.
- mncharity 4y agoSo the concern is overfitting to a single target? Hmm, then perhaps: here are several/parameterized cache models to develop on; one/several will be used to judge the competition? > Cache-oblivious code is a lot more successful [...] Hardwiring code to rely on a rigidly predefined amount of cache is the worst Yes, but ... Creating cache-oblivious code requires devs non-oblivious to cache. Perhaps a kata/competition might encourage such.