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
Typical Power Usage in Data Centres - Practical HVAC
typical power usage in data centres

The pie chart above shows the typical power usage in data centres. The example illustrated above would have a calculated PUE of = 100/54 = 1.852

The lowest hanging fruit to reduce the PUE of a new data centre is reducing its cooling power use by capitalising on free cooling … if weather permits.

Let’s look at the Canberra weather data plot, we can conservatively estimate 90% of the time being able to capitalise on free cooling.

Canberra weather data plot

Based on this, if we reduce the cooling power requirement by half, and everything else remained the same; the resultant PUE will be = 82/54 = 1.519.

Assuming the data centre is 2,000kW, you will use 5,834,160kW/h less energy annually at a saving of $7ook per year (assuming $0.12 per kW/h) and a reduction of about 3,500 tons of carbon. Projecting these to 5 and 10 years, your total cost saving will be $3.5M and $7.0M respectively.

It really pays to be energy efficient and capitalise on net zero energy HVAC technology to improve your data centre ROI.

—————- Contact me to talk about how we can help with your next project, or shoot me a private message. Call me on 04 8888 4839.
Scroll to Top