Maybe after you convince a book to read itself and present you the audio summary. Pretty much the same as what you said there.

Fastest code doesn't even use RAM, latency is too high, and guess what, it's not even needed, and if it unfortunately becomes needed, the speed drops. Like, big time. So, best practice is to limit to maximum any access to RAM. Having exabytes or zettabytes of it does not help with anything here (I hear the "bsgs" whispers, it is indeed a fantastic idea to do lookups in some memory-based huge table, after each EC point gets computed! It definitely won't go all over the place and add latencies).