计算机工程师分级_这些是每个计算机工程师都应该知道的数字
計(jì)算機(jī)工程師分級
In 2010, Jeff Dean from Google gave a wonderful talk at Stanford that made him quite famous. In it, he discussed a few numbers that are relevant to computing systems. Then Peter Norvig published those numbers for the first time on the internet.
2010年，來自Google的Jeff Dean在斯坦福大學(xué)進(jìn)行了精彩的演講，這使他頗有名氣。 在其中，他討論了一些與計(jì)算系統(tǒng)有關(guān)的數(shù)字。 然后，彼得·諾維格(Peter Norvig)首次在互聯(lián)網(wǎng)上發(fā)布了這些數(shù)字。
Time passed, and the numbers changed. Here is a very good interactive web UI of those numbers which roughly tells how much they have changed over the years as a function of time.
時(shí)間過去了，數(shù)字改變了。 這是一個(gè)很好的交互式Web UI ，其中包含這些數(shù)字，可以粗略地說明這些年來這些數(shù)字隨時(shí)間變化了多少。
This article is not only a compilation of Jeff Dean's estimated data, but rather it brings together all such numbers from different sources. This should help you as a system designer and architect. While designing, you can use these numbers to estimate the amount of resources your system needs.
本文不僅是杰夫·迪恩(Jeff Dean)估計(jì)數(shù)據(jù)的匯編，而且還匯集了來自不同來源的所有此類數(shù)據(jù)。 這應(yīng)該可以幫助您作為系統(tǒng)設(shè)計(jì)師和架構(gòu)師。 在設(shè)計(jì)時(shí)，您可以使用這些數(shù)字來估計(jì)系統(tǒng)所需的資源量。
粗略估算2019年的延遲數(shù)據(jù)： (Rough estimation of latency data for 2019:)
Compress 1 KB with Zippy (currently called Snappy): 2000 nanoseconds or 2 microseconds.
使用Zippy(當(dāng)前稱為Snappy )壓縮1 KB：2000納秒或2微秒。
CPU branch mispredict: 3 nanoseconds.
CPU分支預(yù)測錯(cuò)誤 ：3納秒。
有效負(fù)載通過TCP傳輸所花費(fèi)的時(shí)間： (Time Taken for payload to travel over TCP:)
Here is the amount of time required to transmit various data payloads on typical cell networks around the world assuming no data loss.
假設(shè)沒有數(shù)據(jù)丟失，這是在世界各地的典型蜂窩網(wǎng)絡(luò)上傳輸各種數(shù)據(jù)有效載荷所需的時(shí)間。
RTT — Round Trip Time — Total time taken for a data packet (bunch of data bytes) to travel from sender to receiver and receiver to sender over the network. In short, it’s called Ping time.
RTT —往返時(shí)間—數(shù)據(jù)包(數(shù)據(jù)字節(jié)束)在網(wǎng)絡(luò)上從發(fā)送方到接收方以及從接收方到發(fā)送方傳播所花費(fèi)的總時(shí)間。 簡而言之，稱為Ping時(shí)間。
So the greater the response size means more bytes, a longer round trip, more API latency, and ultimately a less user friendly app.
因此，響應(yīng)大小越大，意味著字節(jié)越多，往返時(shí)間越長，API延遲越長，最終導(dǎo)致用戶友好的應(yīng)用程序越少。
This post will be updated when new or updated numbers are found. Please let me know if you are aware of new numbers.
找到新的或更新的號碼后，該帖子將更新。 如果您知道新號碼，請告訴我。
This article is originally published on Author's medium wall. If you like it, please give claps.
本文最初發(fā)表在作者的媒體墻上 。 如果喜歡，請鼓掌。
Reference:
參考：
https://colin-scott.github.io/blog/2012/12/24/latency-trends/
https://colin-scott.github.io/blog/2012/12/24/latency-trends/
https://blog.std.in/2015/05/23/http-response-sizes-and-tcp/
https://blog.std.in/2015/05/23/http-response-sizes-and-tcp/
https://medium.com/@kousiknath/must-know-numbers-for-every-computer-engineer-6338a12c292c
https://medium.com/@kousiknath/must-know-numbers-for-every-computer-engineer-6338a12c292c
翻譯自: https://www.freecodecamp.org/news/must-know-numbers-for-every-computer-engineer/
計(jì)算機(jī)工程師分級
總結(jié)
以上是生活随笔為你收集整理的计算机工程师分级_这些是每个计算机工程师都应该知道的数字的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。
- 上一篇： 梦到香蕉打什么奖
- 下一篇： 验证曲线和学习曲线_如何击败技术学习曲线