[.net] Cache-Oblivious Data Structures and Algorithms

The answer is to profile your code. Especially if you can come up with multiple algorithms to do the same thing, then you can compare the results and draw your own conclusions for your own scenario

Quote:

Original post by joelmartinez The answer is to profile your code. Especially if you can come up with multiple algorithms to do the same thing, then you can compare the results and draw your own conclusions for your own scenario

I'm sorry but that is not the kind of answer i was looking for, i already profile code and yes i can look at memory usage but that doesn't really help me from possibly wasting time going head and code cache-oblivious implementations then finding out it was pointless.

I would like more details than this.