TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Google's Numbers Every Developer Should Know

9 pointsby thedobover 16 years ago

3 comments

blurryover 16 years ago
Please don't post a link to your own blog when all it does is link to another post. Just link to the original.
评论 #487730 未加载
azanarover 16 years ago
He may have meant this when he created the slide, but precise numbers here seem less important than relative magnitude as long as one is reasonably close.<p>One could be a few ns off on how long a L2 cache lookup takes, and endure in all but the most time-critical situations. Far bigger problems occur when one failed to account for drive seeks being around eight orders of magnitude slower than L2 cache lookups.<p>It doesn't strike me as a list of numbers to memorize and be able to recite, but more the sake of cultivating an intuition of where to start looking for places to optimize communication, and the relative order of things one should focus on.
Tichyover 16 years ago
"# Read 1 MB sequentially from network 10,000,000 ns # Read 1 MB sequentially from disk 30,000,000 ns"<p>That seems weird - wouldn't the 1MB be read from a disk at the other end of the network? So how can disk be slower than network (unless the network is all RAM-Disk...).
评论 #488202 未加载