Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wishlist-member domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/prachvac/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the loginizer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/prachvac/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/prachvac/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/prachvac/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/prachvac/public_html/wp-includes/functions.php on line 6114
Data Centre Temperature and Humidity Best Practice

Data Centre Temperature and Humidity Best Practice

Data Centre Temperature and Humidity

I have been asked many times over; what is data center temperature and humidity best practice? And have debated with my colleagues on why we should not be designing data centres at 18-20°CdB and 50% RH as we used to.

In data centres cooling designs, it’s not about the supply temperature, what really matters is the hot air containment and treatment. If you understand this, it will help you see my points and how you will be able to capitalise on these reasons to differentiate designs.

Here are the why for my design temperature and humidity

  1. will be able to save on running cost at an elevated supply air temperature and a higher temperature difference
  2. will be able to capitalise on an extended period of free cooling
  3. will be able to keep the cooling system as simple as I possibly can
  4. want to be environmentally friendly to the best of my ability using R718
  5. want to be compressor-less
  6. want to simplify maintenance

Ultimately, it’s really all about the PUE (Power Utilisation Effectiveness) and DCiE (Data Center Infrastructure Efficiency). Coming back to the question at hand, what are the data centre temperature and humidity best practice?

Data Center Temperature and Humidity Best Practice in Brief

Let’s take a look at Table 1 ASHRAE 2008 Thermal Guidelines for Data Centres
data center cooling
Based on this table, I would say ranging from 18°Cdb to 27°Cwb and 20% to 80% Relative Humidity (RH) for the most stringent environmentally controlled data centres, this is not much of guidance, isn’t it?

Now, let’s look at humidity first, the key to relative humidity selection is really ‘non-condensing‘, which effectively meant control of the maximum allowable dew point temperature within the conditioned space! So as long as you can ensure no condensation will occur inside your data center, you will satisfy your equipment supply vendor’s criteria on relative humidity. In actual fact, I would prefer to specify dew point temperature rather than relative humidity.

The level of temperature and relative humidity control will depend on your data centre class, here is another guideline from ASHRAE for information.
ASHRAE Thermal Guidelines Data Centres Class Comparison
Even back in 2011, my internal design temperature criteria were 27°Cdb, using indirect heat mass exchanger or some would fondly call it indirect “swamp coolers”. Why 27°Cdb?
  1. is because it’s still within the guideline provided by ASHRAE
  2. is if you look at equipment specifications on operating conditions, you will see that most of these modern servers, switches and etc have maximum operating temperatures around 40°C and some even at 45°C.

Let’s take a peek into Google’s data centre, on what is their internal design temperature … just fast forward to the 2:50 mark.

If Google is designing its data centres at 27°C (80°F), why aren’t you? … but hey why stops at 27°C, Microsoft is pushing it up to 32°C (90°F). Isn’t it time you re-think about your data centre cooling strategies?

With operating temperature ranging from 27 to 32°C and relative humidity up to 90% non-condensing, what is better than indirect evaporative cooling to air condition your data center?

Related

Scroll to Top