Intel’s Experiment on Free Cooling to 90 degrees

Intel has announced the results of experiment that challenged myths about server room cooling:

  • The chipmaker’s air-economizer experiment reveals that servers can weather relatively harsh conditions while delivering huge savings on cooling
  • For 10 months, the chipmaker had 500 production servers, working at 90 percent utilization, cooled almost exclusively by outside air at a facility in New Mexic
  • Only when the temperature exceeded 90 degrees Fahrenheit did they crank on some artificial air conditioning. Intel did very little to address air-born contaminants and dust, and nothing at all to deal with fluctuating humidity
  • The result: a slightly higher failure rate – around 0.6 percent more – among the air-cooled servers compared to those in the company’s main datacenter – and a potential savings of $2.87 million per year in a 10MW datacenter using free cooling over traditional cooling.

The computer industry has a practice of keeping data centres under 70F/21C. The University of Winnipeg Library server room runs around 90F/30C on an average day. Our mean time to failure (MTTF) on drives and blistering capacitors on motherboards has been no where near industry standard reports.  Perhaps it is a myth and the hotter, the better…or perhaps we’re just too lucky. We’ve been running about 10 servers in the server room for about four years now, so we’ll have to see if they start to get a bit more cranky as they get a bit older.

Library-related API’s

Thanks to Roy Tennant for compiling a list of Library-related API’s.  From a variety of services that can validate and be used to leverage additional information to a number of tools and specifications, this is a handy list of a number of essential API’s that can be used by many Libraries.

For those not familiar with them, an application programming interface (or API) is a set of functions, procedures, methods or classes that an operating system, library or service provides to support requests made by computer programs.  Submit a chunk of data like an ISBN and an API can return a title and perhaps other related data.  This is an oversimplication as many services like Amazon Web Services (AWS) API can handle many different types of data and respond handily with standardized output.  Submission interfaces are often avoided with API’s and data is returned in a format like XML that can be more easily repurposed than an HTML results page.  API’s have become quite fasionable with major Internet players like Google and Amazon and Facebook making their API’s widely available to developers.  As indicated by part of the list compiled by Roy, there are many Library-oriented API’s based on standards like Z39.50 or OAI that have been developed by Libraries and are often forgotten with all the big Internet players.

Historic ‘Blockbuster’ Store Offers Glimpse Of How Movies Were Rented In The Past

Historic “Blockbuster” Store Offers Glimpse Of How Movies Were Rented In The Past (runtime 1:59)

….Hmmm….And, by extension, I could see someone creating a mockumentary for Libraries.  Of course, perhaps someone could work on the Shopping Mall mockumentary in the same respect.

In this mockumentary, the person acting as an ‘actual Blockbuster employee named Jerome’ states, “My main responsibilities are to man the cash register and to take the movies from the return slot back onto the shelves.”  Obviously, this is similar function served by circulation clerks and shelving technicians in many of our Libraries.  Albeit, this is an oversimplified summary of a job description that does maximize the humour in the situation, but, sadly, as we continue to move from brick and mortar Libraries to more virtual or digital Libraries, such functions are still essential. Moving physical bits in the traditional business model is unavoidable, but as our practice becomes more and more digital and new models and practices evolve, the juxtaposition of these two worlds can become much more glaring.

To the tour group, one character states: “I am a blockbuster customer named Cathy. Two times a week a travel six miles to rent and return videos. Oh, look we’re in the Comedy section.”  Again, the similarities between the old world video store are not unlike traditional Libraries (or even brick and mortar stores for that matter).  Expecting people to travel ‘great’ distances and then look for an item that may be located in a seemingly arbitrarily location due to a limitation imposed by the physical medium is obviously very similar to the old brick and mortar Library experience.

As Cathy states “What’s so poignant about this time is the uncertainty: When you get to the Blockbuster, are they going to have your video? Did someone else rent it? Is there a line? Are the alarms going to sound, when you walk out the front door? It was very difficult for the people that lived during this era.”  Again, requirements of making any physical medium available impose some restrictions and require certain business processes or policies and practices to be created, but even as this video pokes fun at the historic Blockbuster, we have to wonder what kind of legacy would be left by a mockumentary of Libraries.

As Jerome states to Cathy:  “Yes, we have it, but our only copy is checked out.”  Though we all face limitations with the physical nature of our historical Libraries, hopefully we can do better at making things less difficult for our patrons so watching such a video wouldn’t seem so mocking.

Follow

Get every new post delivered to your Inbox.