4 ms·
I think the author assumed readers were programmers. That's OK in a trade publication. Indeed, every programmer should know those numbers.
by wingo 16y ago
I think the author assumed readers were programmers. That's OK in a trade publication.
Indeed, every programmer should know those numbers.
- bigiain 16y agoThere's still an argument to be made that it's largely esoteric even for programmers. There's an enormously large cross section of professional programmers for whom this is really only relevant to satisfy some curiosity rather than in any way relevant to their day to day coding. There's 100% no use in knowing the difference between an L1 and L2 cache hit compared to a branch misprediction if your day job involves, say, writing Wordpress plugins in php or iOS apps or maintaining some corporate Java app.
- robryan 16y agoYour right that you can't really think about this stuff to much sitting in a high level language. It is useful though to have a good idea of the underlying architecture which your taking advantage of at a higher level. Sure L1 and L2 cache optimization is out of your hands but if you are writing an app for the GAE knowing the relative speeds of writes in relations to reads could influence the decisions you make.