4 ms·
Google's quarterly revenue is roughly $20B[1] - that's $80B per year. I think that it is perfectly plausible that an engineer could achieve a 0.125% increase in
by uiri 10y ago
Google's quarterly revenue is roughly $20B[1] - that's $80B per year. I think that it is perfectly plausible that an engineer could achieve a 0.125% increase in yearly revenue. Now, disentangling that from other possible contributing factors, getting the right visibility from management, etc. is distinct from that.
I have no problem believing that MapReduce contributed $XB to Google's revenue over the course of the past 20 years.
[1] https://www.sec.gov/Archives/edgar/data/1652044/000165204416000021/goog10-qq12016.htm#s19787FEDB03F2F55A3452F03D6A7DC1C https://www.sec.gov/Archives/edgar/data/1652044/000165204416...
- CalChris 10y agoMapReduce was published in 2004. The paper was two people; the implementation was probably a lot more. Even then, it was just a re-engineering of an earlier code base (read that as multiple available cat skinning technologies). By 2014, it was no longer used, so that's 10 years. Lastly, it wasn't exactly novel. https://en.wikipedia.org/wiki/MapReduce#Lack_of_novelty https://en.wikipedia.org/wiki/MapReduce#Lack_of_novelty FWIW, it appears they're giving away the TensorFlow stuff because they lost the mindshare battle between MapReduce+Hadoop and don't want that to happen again. Again, the $100M figure is an easy (heroic) claim to make but hard to substantiate. Shit's hard. Big shit is really hard.
- londons_explore 10y ago> By 2014, it was no longer used [Citation needed]
- CalChris 10y agohttp://www.datacenterknowledge.com/archives/2014/06/25/google-dumps-mapreduce-favor-new-hyper-scale-analytics-system/ http://www.datacenterknowledge.com/archives/2014/06/25/googl...
- dekhn 10y agoYou basically don't know what you're talking about, factually speaking, along a wide range of fact dimensions.
- CalChris 10y agoGood to know that. I was worried.