5 ms·
>> internal cheat sheet of "numbers every engineer should know" which included the cost in dollar terms Would love to see that. For companies determining what'
by dhruvkar 7y ago
>> internal cheat sheet of "numbers every engineer should know" which included the cost in dollar terms
Would love to see that. For companies determining what's worth what, this would be great to see, even just for the format.
- SquishyPanda23 7y agoThe Jeff Dean version is public, but does not include cost in dollars https://youtu.be/modXC5IWTJI?t=3548 https://youtu.be/modXC5IWTJI?t=3548
- nostrademons 7y agoThe format is IIRC something like: 1 engineer-hour = W ms/search of latency X GB-year of RAM Y CPU-years of processing time Z TB-year of hard disk space etc. The actual numbers are very confidential, I've forgotten them, and they're probably different from when I was there. Basically, everything is computed in dollar terms and normalized to engineer time. You assume your code will live for a certain lifetime (a year seemed reasonable when I was there), and you know how many queries your service currently gets (that's another number-you-should-know: usage data for the product you're working on). Multiply out the CPU usage increase by number of queries to get total CPU increase (you need this for capacity planning anyway), and you can compare that to the number of engineer-hours spent working on it to get cost effectiveness.