> The % of programmers that actually need to know any of these numbers is tiny. If you mean the whole range of values I would agree. However, once I've interv

> The % of programmers that actually need to know any of these numbers is tiny. If you mean the whole range of values I would agree. However, once I've interviewed a developer for a front-end position that was entirely oblivious to the cost of making an HTTP request, firmly believing that only large downloads had any measurable impact on performance. Even if you do not have to do back-of-the-napkin calculations on cache latency, knowing the relative cost of each of these operations does wonders to your decision process.