Jump to content

Urs Hölzle

From Wikipedia, the free encyclopedia
(Redirected from Urs Hoelzle)
Urs Hölzle
Urs Hölzle (2014)
Born1964 (age 59–60)
Basel, Switzerland
Alma materETH Zurich
Stanford University
Known forJIT compilers, data centers, cloud computing, Google Cloud Platform
AwardsAAAS Fellow, ACM Fellow, Fulbright Scholar, NAE Member
Scientific career
InstitutionsUniversity of California, Santa Barbara
Google
ThesisAdaptive optimization for Self: Reconciling High Performance with Exploratory Programming (1994)
Doctoral advisorDavid Ungar
John L. Hennessy

Urs Hölzle (German pronunciation: [ˈʊrs ˈhœltslɛ]; born 1964[1]) is a Swiss-American software engineer and technology executive. As Google's eighth employee and its first VP of Engineering, he has shaped much of Google's development processes and infrastructure, as well as its engineering culture.[2] His most notable contributions include leading the development of fundamental cloud infrastructure such as energy-efficient data centers, distributed compute and storage systems, and software-defined networking. Until July 2023, he was the Senior Vice President of Technical Infrastructure and Google Fellow at Google. In July 2023, he transitioned to being a Google Fellow only.[3][4]

Career

[edit]

Before joining Google, Hölzle was an associate professor of computer science at University of California, Santa Barbara. He received a master's degree in computer science from ETH Zurich in 1988 and was awarded a Fulbright scholarship that same year. In 1994, he earned a Ph.D. from Stanford University, where his research focused on programming languages and their efficient implementation. Via a startup founded by Hölzle, David Griswold, and Lars Bak (see Strongtalk), that work then evolved into a high-performance Java VM named HotSpot, acquired by Sun's JavaSoft unit in 1997 and from there became Sun's premier JVM implementation.

In 1999 he joined Google and became its first Vice President of Engineering later that year and influenced Google's corporate and engineering culture.[2] While he led various areas during the early years of the company, including operations, search, and Gmail, he is best known for his work leading the infrastructure systems underpinning Google's applications, and for their focus on both efficiency and scalability. With Jeff Dean and Luiz Barroso he designed the initial distributed architecture for Google.[5] This work was recognized by the Association for Computing Machinery who named him a Fellow for the design, engineering and operation of energy efficient large-scale cloud computing systems.[6] He is also credited for creating Google Gulp for April Fool's Day in 2005.

Data centers and servers

[edit]

He led the design of Google's efficient data centers which are said to use less than half the power of a conventional data center.[7] In 2014 he received The Economist's Innovation Award for his datacenter efficiency work.[8] With Luiz Barroso, he wrote The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines.[9] Now in its third edition, the book is the most downloaded textbook at Morgan Claypool[10] and is widely used in undergraduate and graduate Computer Science education. For his contributions to the design, operation, and energy efficiency of large-scale data centers, Hölzle was elected into the National Academy of Engineering in 2013.[11]

In June 2007, he introduced the Climate Savers Computing Initiative together with Pat Gelsinger which aimed to halve the power consumption of desktop computers and servers. In 2012, after mobile computing and enhanced awareness of datacenter energy costs had contributed to significant improvements in energy efficiency, CSCI merged with the Green Grid consortium.[12]

Also in 2007, he and Luiz Barroso wrote "The Case for Energy Proportional Computing" which argued that servers should be designed to use power in proportion to their current load, because they spend much of their time being only partially loaded. This paper is often credited for spurring CPU manufacturers to make their designs much more energy efficient.[13] Today, energy proportional computing has become a standard goal for both server and mobile uses.

Networking

[edit]

Starting in 2005, Hölzle's team began to develop datacenter networking hardware because off-the-shelf network equipment could not scale to the demands of large data centers. Using Clos network topologies based on commodity switch chips, these datacenter networks scaled from an initial 10 Tbit/s to 1,000 Tbit/s a decade later.[14] Initially esoteric and kept a secret[citation needed], today this approach is standard for large datacenter networks; virtually all hyperscale datacenter operators use similar approaches.[15][16]

In 2012, Hölzle introduced "the G-Scale Network" on which Google had begun managing its petabyte-scale internal data flow via OpenFlow, an open source software system jointly devised by scientists at Stanford and the UC Berkeley and promoted by the Open Networking Foundation. In 2021, this work was recognized by the ACM SIGCOMM Networking Systems Award.[17] The internal data flow, or network, is distinct from the one that connects users to Google services (Search, Gmail, YouTube, etc.). In the process of describing the new network, Hölzle also confirmed more about Google's making of its own networking equipment like routers and switches for G-Scale; and said the company wanted, by being open about the changes, to "encourage the industry — hardware, software and ISP's — to look down this path and say, 'I can benefit from this.'" He said network utilization was nearing 100% of capacity, a dramatic efficiency improvement.[18]

Google's teams also heavily contributed to software-defined networking, creating or contributing to key building blocks used in many networks today, including OpenConfig for vendor-neutral, model-driven network management; gRPC for fast RPCs, protobuf for data interchange, OpenTelemetry for tracing, and the Istio service mesh.

Cloud computing

[edit]

Hölzle is credited with leading the creation of Google's internal cloud, including architecting clusters based on commodity servers,[19] distributed file systems,[20][21] cluster scheduling,[22] software defined networking,[23][24][25] hardware reliability,[26] processor design,[27][28] custom ASICs for AI (TPUs) and vide processing,[29] and many more. One of the most notable events from this period was the emergence of Kubernetes, a project funded by Hölzle.[30]

Google's internal cloud doesn't use virtualization, but product development on an external cloud platform started in 2014, leading to the launch of the Google Cloud Platform in 2016. Hölzle is also credited with changing Google Cloud's engineering culture to "to make the transition from niche cloud to enterprise class cloud".[4]

Environmental work

[edit]

In 2007, Hölzle announced that Google would be carbon neutral starting that year, using individually selected and monitored carbon offset projects.[31] In the same year, Google started the RE<C initiative ("Renewable Energy less than (cheaper than) coal")[32] to develop cheaper forms of renewable energy, but four years later Hölzle announced the end of that strategy, dropping development of "solar thermal" electricity (for example with BrightSource Energy) because it was not keeping pace with the rapid price decline of another solar technology – photovoltaics.[33]

Starting in 2010,[34] Google began buying renewable energy from new wind and solar farms to cover the energy needs for all its datacenters.[35] In 2017, Hölzle received the CK Prahalad Award "for bringing about innovations and radical efficiencies in data center technology and increasing corporate purchasing of renewable energy" and for "not only accelerating Google’s sustainability, [but] also cutting a path for other companies to follow suit.”[36] While purchases initially were small, they created a market for corporate renewable energy purchases that has become very influential in driving the overall growth of renewable energy purchases. For example, SP Global reports that the top hyperscalers (Amazon, Google, Meta, Microsoft) accounted for over 40% of contracted capacity during 2017-22.[37]

In 2017 Google reached enough renewable energy to offset 100% of its usage[38] and now is the world's largest corporate buyer of renewable energy.[39] After reaching 100% renewables at an annual average level, Google has pursued an additional focus on 24/7 carbon free energy, i.e., actually running on 100% renewable energy every hour of every day.[40][41][42][43][44][45] As of 2022, seven Google datacenter regions reached 90% or more carbon-free energy, and thirteen reached more than 85%. Hölzle has widely been credited for favoring market based approaches, discouraging proprietary paths that would only benefit Google. As a result, organizations like the Clean Energy Buyers Alliance, the European 24/7 CFE Hub, and the United Nations 24/7 Carbon-Free Energy Compact now focus on enabling any company to pursue their own carbon-free energy goals.

In 2022, Hölzle was revealed as the primary investor behind the New Zealand based solar developer Helios which aims to build about 10 grid-connected solar farms across New Zealand.[46]

He is a board member of the US World Wildlife Fund.[47]

Academic honors

[edit]

Hölzle became a Fulbright scholar in 1988 and was elected a member of the National Academy of Engineering in 2013 for contributions to the design, operation, and energy efficiency of large-scale data centers.[11] He also is a Fellow of the Association for Computing Machinery (2009),[48] the AAAS (2017),[49] and the Swiss Academies of Arts and Sciences.[50]

Google culture

[edit]

As Google's eighth employee and its first VP of Engineering, Hölzle shaped much of Google's development processes and infrastructure. In a book about the early days of Google, Doug Edwards credits him with defining much of Google's engineering and corporate culture.[2] For example, he is said to have instituted Google's practice of code reviews for every change, the culture of using blameless postmortems to learn from mistakes rather than find out whose fault it was,[51] and a focus on using technical interviews to identify the best candidates. He recruited many of Google's early engineers, including Jeff Dean.

He was known for his self-deprecating humor; for example, his initial job title was Search Engine Mechanic "because everything was broken".[52]

Hölzle also influenced Google's office culture by bringing his dog Yoshka to work. In 2004 Yoshka even "authored" a blog post, and today Google declares itself a "dog company".[53] The cafe in Building 43 of the Googleplex is named Yoshka's Cafe[54] in honor of Google's first dog.

In July 2021 he was criticized[55] for a perceived 'hypocritical' approach to remote working; opposing it strongly for others, while relocating to New Zealand. However, shortly after Hölzle's transfer was announced, Google approved the large majority of employee applications, permitting 8,500 other employees to work remotely as well.[56]

References

[edit]
  1. ^ Seydtaghia, Anouch (2022-06-19). "Urs Hölzle: "Google devient de plus en plus efficace"" [Urs Hölzle: "Google is becoming more and more efficient"]. Le Temps (in French). ISSN 1423-3967. Archived from the original on 2023-09-20.
  2. ^ a b c Edwards, Douglas (2011). I'm Feeling Lucky: The Confessions of Google Employee Number 59. Houghton Mifflin Harcourt. ISBN 978-0-547-41699-1.
  3. ^ "Urs Hölzle on LinkedIn: I wanted to share some thoughts on becoming an engineer again after having… | 112 comments". www.linkedin.com. Retrieved 2023-07-17.
  4. ^ a b Miller, Ron (2023-07-12). "Google Cloud infrastructure head Urs Hölzle stepping down". TechCrunch. Retrieved 2023-07-17.
  5. ^ Barroso, L.A.; Dean, J.; Holzle, U. (March 2003). "Web search for a planet: The Google cluster architecture". IEEE Micro. 23 (2): 22–28. doi:10.1109/MM.2003.1196112. ISSN 1937-4143.
  6. ^ "Urs Hoelzle". awards.acm.org. Retrieved 2021-05-01.
  7. ^ Google's Green Datacenter
  8. ^ Economist, December 6, 2014
  9. ^ Barroso, Luiz André; Hölzle, Urs (2009). "The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines". Synthesis Lectures on Computer Architecture. 4: 1–108. doi:10.2200/S00193ED1V01Y200905CAC006.
  10. ^ "- Most Read Papers". www.morganclaypool.com. Retrieved 2022-12-08.
  11. ^ a b > NAE press release
  12. ^ "The Green Grid and Climate Savers Will Merge". Data Center Knowledge | News and analysis for the data center industry. 2012-07-20. Retrieved 2022-11-18.
  13. ^ "Server Efficiency: Aligning Energy Use With Workloads", Datacenter Knowledge, June 12, 2012
  14. ^ Singh, Arjun; Ong, Joon; Agarwal, Amit; Anderson, Glen; Armistead, Ashby; Bannon, Roy; Boving, Seb; Desai, Gaurav; Felderman, Bob; Germano, Paulie; Kanagala, Anand; Provost, Jeff; Simmons, Jason; Tanda, Eiichi; Wanderer, Jim (2015). "Jupiter Rising: A Decade of Clos Topologies and Centralized Control in Google's Datacenter Network". Proceedings of the 2015 ACM Conference on Special Interest Group on Data Communication. pp. 183–197. doi:10.1145/2785956.2787508. ISBN 978-1-4503-3542-3. S2CID 2817692.
  15. ^ "Introducing data center fabric, the next-generation Facebook data center network". Facebook Engineering. 2014-11-14. Retrieved 2021-05-01.
  16. ^ Jain, Sushant; Kumar, Alok; Mandal, Subhasree; Ong, Joon; Poutievski, Leon; Singh, Arjun; Venkata, Subbaiah; Wanderer, Jim; Zhou, Junlan; Zhu, Min; Zolla, Jon (2013-08-27). "B4: experience with a globally-deployed software defined wan". ACM SIGCOMM Computer Communication Review. 43 (4): 3–14. doi:10.1145/2534169.2486019. ISSN 0146-4833.
  17. ^ "SIGCOMM Networking Systems Award | acm sigcomm". www.sigcomm.org. Retrieved 2022-04-01.
  18. ^ Levy, Steven, "Going With the Flow: Google's Secret Switch to the Next Wave of Networking", Wired, April 17, 2012. Retrieved 2012-04-17.
  19. ^ Barroso, Luiz Andre; Dean, Jeffrey; Hölzle, Urs (2003). "Web Search for a Planet: The Google Cluster Architecture". IEEE Micro. 23 (2): 22–28. doi:10.1109/MM.2003.1196112.
  20. ^ "Google File System", Wikipedia, 2023-04-27, retrieved 2023-07-17
  21. ^ Metz, Cade. "Google Remakes Online Empire With 'Colossus'". Wired. ISSN 1059-1028. Retrieved 2023-07-17.
  22. ^ Verma, Abhishek; Pedrosa, Luis; Korupolu, Madhukar R.; Oppenheimer, David; Tune, Eric; Wilkes, John (2015). "Large-scale cluster management at Google with Borg". Proceedings of the Tenth European Conference on Computer Systems. Bordeaux, France. pp. 1–17. doi:10.1145/2741948.2741964. ISBN 9781450332385. S2CID 1149996.{{cite book}}: CS1 maint: location missing publisher (link)
  23. ^ OpenFlow @ Google - Urs Hoelzle, Google, 7 May 2012, retrieved 2023-07-17
  24. ^ Jain, Sushant; Kumar, Alok; Mandal, Subhasree; Ong, Joon; Poutievski, Leon; Singh, Arjun; Venkata, Subbaiah; Wanderer, Jim; Zhou, Junlan; Zhu, Min; Zolla, Jon; Hölzle, Urs; Stuart, Stephen; Vahdat, Amin (2013-08-27). "B4: experience with a globally-deployed software defined wan". ACM SIGCOMM Computer Communication Review. 43 (4): 3–14. doi:10.1145/2534169.2486019. ISSN 0146-4833.
  25. ^ Singh, Arjun; Ong, Joon; Agarwal, Amit; Anderson, Glen; Armistead, Ashby; Bannon, Roy; Boving, Seb; Desai, Gaurav; Felderman, Bob; Germano, Paulie; Kanagala, Anand; Provost, Jeff; Simmons, Jason; Tanda, Eiichi; Wanderer, Jim (2015-08-17). "Jupiter Rising: A Decade of Clos Topologies and Centralized Control in Google's Datacenter Network". ACM SIGCOMM Computer Communication Review. 45 (4): 183–197. doi:10.1145/2829988.2787508. ISSN 0146-4833.
  26. ^ Pinheiro, Eduardo; Weber, Wolf-Dietrich; Barroso, Luiz André (2007). "Failure Trends in a Large Disk Drive Population". 5th USENIX Conference on File and Storage Technologies (FAST 2007): 17–29.
  27. ^ Hölzle, Urs. "Brawny cores still beat wimpy cores, most of the time" (PDF). IEEE Micro. 30 (4): 20–24.
  28. ^ "Energy proportional computing", Wikipedia, 2023-06-07, retrieved 2023-07-17
  29. ^ Ranganathan, Parthasarathy; Stodolsky, Daniel; Calow, Jeff; Dorfman, Jeremy; Guevara, Marisabel; Smullen IV, Clinton Wills; Kuusela, Aki; Balasubramanian, Raghu; Bhatia, Sandeep; Chauhan, Prakash; Cheung, Anna; Chong, In Suk; Dasharathi, Niranjani; Feng, Jia; Fosco, Brian (2021-04-17). "Warehouse-scale video acceleration: Co-design and deployment in the wild". Proceedings of the 26th ACM International Conference on Architectural Support for Programming Languages and Operating Systems. New York, NY, USA: Association for Computing Machinery. pp. 600–615. doi:10.1145/3445814.3446723. ISBN 978-1-4503-8317-2. S2CID 232165381.
  30. ^ "All I really need to know I learned from co-founding Kubernetes". www.linkedin.com. Retrieved 2024-06-08.
  31. ^ "Carbon neutrality by end of 2007". Official Google Blog. Retrieved 2022-12-08.
  32. ^ "Philanthropy Programs for Underserved Communities - Google.org". www.google.org. Retrieved 2022-12-08.
  33. ^ "Google cans concentrated solar power project | REVE News of the wind sector in Spain and in the world". 24 November 2011. Retrieved 2022-12-08.
  34. ^ "Google inks 20-year deal to buy wind power for data centers | InfoWorld". www.infoworld.com. Retrieved 2022-12-08.
  35. ^ Google's Green PPAs https://static.googleusercontent.com/media/www.google.com/en//green/pdfs/renewable-energy.pdf
  36. ^ "C.K. Prahalad Award". CEF. Retrieved 2022-05-17.
  37. ^ "Global corporate clean energy procurement crosses 50 GW with Asia as the largest region in 2022". IHS Markit. 2023-03-02. Retrieved 2023-09-12.
  38. ^ "Clean Energy: Renewable Energy Milestone". Google Sustainability. Retrieved 2022-12-08.
  39. ^ "Tech giants power record surge in renewable energy sales". the Guardian. 2020-01-28. Retrieved 2022-12-08.
  40. ^ "100% renewable is just the beginning". Google Sustainability. Retrieved 2023-09-12.
  41. ^ "Aiming to Achieve Net-Zero Emissions - Google Sustainability". Sustainability. Retrieved 2023-09-12.
  42. ^ "How carbon-free energy around the clock can work". Google. 2022-10-11. Retrieved 2023-09-12.
  43. ^ Gordon, Oliver (2022-11-03). "Is '24/7 carbon-free energy' the new gold standard of decarbonisation?". Energy Monitor. Retrieved 2023-09-12.
  44. ^ "24/7 Carbon-Free Energy". World Resources Institute. 2023-02-07. Retrieved 2023-09-12.
  45. ^ "Tracking Our Carbon-Free Energy Progress". Google Sustainability. Retrieved 2023-09-12.
  46. ^ Pullar-Strecker, Tom (2022-04-18). "Top Google exec backs $1.3 billion investment in NZ solar power". Stuff. Retrieved 2023-02-22.
  47. ^ "Urs Hölzle | Leaders | WWF". World Wildlife Fund. Retrieved 2022-12-08.
  48. ^ ACM Fellows>Urs Hoelzle, Association for Computing Machinery webpage.
  49. ^ AAAS 2017 Fellows, AAAS webpage.
  50. ^ Full members>Hölzle, Dr Urs, SATW webpage.
  51. ^ "Site Reliability Engineering, Chapter 15 - Postmortem Culture: Learning from Failure". sre.google. Retrieved 2021-05-30.
  52. ^ magazin, Andrea Rungg, manager (16 July 2015). "Urs Hölzle: Googles Mitarbeiter Nummer 8". www.manager-magazin.de (in German). Retrieved 2021-05-30.{{cite web}}: CS1 maint: multiple names: authors list (link)
  53. ^ "Working from home is ruff. Dooglers make it a little better". Google. 2020-10-16. Retrieved 2021-05-30.
  54. ^ "Yoshka's · Mountain View, CA 94043". Yoshka's · Mountain View, CA 94043. Retrieved 2021-05-30.
  55. ^ "Google's 'hypocritical' remote work policies anger employees". Retrieved 2021-07-09.
  56. ^ "Bloomberg - Google Approves Most Staff Requests to Relocate or Work Remotely". Bloomberg. 3 August 2021. Retrieved 2021-12-26.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Urs_Hölzle&oldid=1261193230"