Goto

Collaborating Authors

 server part


Microsoft uses AI to boost its reuse, recycling of server parts

#artificialintelligence

Microsoft is bringing artificial intelligence to the task of sorting through millions of servers to determine what can be recycled and where. The new initiative calls for the building of so-called Circular Centers at Microsoft data centers around the world, where AI algorithms will be used to sort through parts from decommissioned servers or other hardware and figure out which parts can be reused on the campus. Microsoft says it has more than three million servers and related hardware in its data centers, and that a server's average lifespan is about five years. Plus, Microsoft is expanding globally, so its server numbers should increase. Circular Centers are all about quickly sorting through the inventory rather than tying up overworked staff.


Microsoft uses AI to boost its reuse, recycling of server parts

#artificialintelligence

Microsoft is bringing artificial intelligence to the task of sorting through millions of servers to determine what can be recycled and where. The new initiative calls for the building of so-called Circular Centers at Microsoft data centers around the world, where AI algorithms will be used to sort through parts from decommissioned servers or other hardware and figure out which parts can be reused on the campus. Microsoft says it has more than three million servers and related hardware in its data centers, and that a server's average lifespan is about five years. Plus, Microsoft is expanding globally, so its server numbers should increase. Circular Centers are all about quickly sorting through the inventory rather than tying up overworked staff. Microsoft plans to increase its reuse of server parts by 90% by 2025.


Putting Machine Learning in Production

@machinelearnbot

In this article, we will discuss how to go from the research phase to the production phase for ML projects and what are the different options to do so. If you try to have your training and server code in the same repository you would probably end up with a big mess that is hard to maintain. Training models and serving real-time prediction are extremely different tasks and hence should be handled by separate components. Last but not least, there is a proverb that says "Don't s**t where you eat", so there's that too. Thus, a better approach would be to separate the training from the server.