3 ms·

Wouldn't column stores be better for the cache?

• cmrdporcupine 5y ago
  I think the answer to that is just: it depends. Again comes back to usage patterns. Yes, if you're doing aggregation operations on a small number of columns then I expect locality of reference could be better with a column-store, rather than thrashing through row-retrievals one after another (and then just throwing them away after aggregating). But if you're frequently doing "look up this customer and others like them" and then using the bulk of the information there? I'd expect better cache behaviour out of row oriented storage. But these days it's so unclear what's happening inside the actual "black box" that is our hardware that it's hard to make generalizations.