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
Best practice datacentres - Practical HVAC
[the_ad id="5239"]

Back in 2011, Facebook already built datacentres with performance metric as below;

  • PUE (power usage effectiveness) of 1.07 at full load.
  • WUE (water use effectiveness) of 0.31 liters/kWH (see the Summary below).
  • CapEx lowered by 45%, and reduced OpEx.
  • Higher reliability due to its simpler construction.

… but why are we still struggling with PUE of 1.3 or more in Australia? Worst, there are many that has PUE of 2 or more!

 

What can you do to reduce your PUE?
For a start, get rid of your chiller, get rid of your cooling towers, get rid of your pumps, get rid of your pipe works, get rid of your duct works!

Connect with me to find out more on how you can reduce your current PUE before you even contemplate on your next data centre or read data center temperature and humidity best practice.

Prineville data center mechanical design features

Facebook Prineville data center mechanical design features.

Read more: Fan wall

[the_ad id="5248"]
Scroll to Top