I was hoping to write a brief two part overview of how to configure the various power settings for the Intel® Xeon Phi™ coprocessor. It was going to be concise and brief, allowing me to get on to the next topic. Unfortunately, as I dug into the topic further, I discovered that much of it is not very well documented. I found myself essentially writing quite a bit of explanation.
As usual, I am starting off writing this as a series of blogs. At a later point, I will reformat the blogs into a more formal article with any semblance of humor removed.
Recently we posted the “Windows* 8 Tutorial: Writing a Multithreaded Application for the Windows Store* using Intel® Threading Building Blocks”. There we stated that the parallel calculation engine can be ported easily to other mobile or desktop platforms. Android is a good example of such a mobile platform.
Developers have substantially improved the performance and power usage of websites and the browsers themselves in recent years. However, this improvement is limited to the factors that browsers can control. Web developers also have a significant ability to improve the performance and power of their websites by making efficient use of resources.
Contrat de licence:
The previous blog in this series, “Intel® Xeon Phi™ coprocessor Power Management Turbo Part 1: What is turbo? And how will it affect my horsepower?” can be found at http://software.intel.com/en-us/blogs/2013/09/26/intel-xeon-phi-coprocessor-power-management-turbo-part-1-what-is-turbo-and-how-will.
Power consumption is a common and growing concern in large compute installations, whether they be HPC, Cloud or Enterprise: facility power and space limitations are making it increasingly difficult to support the explosive growth of computational needs. Thus we need to dig deeper on how to best reduce power consumption at multiple levels, from hardware to software. In this article I will describe some of the known approaches and tools available to tackle this challenge.
I had an interesting question come across my desk a few days ago: “Is it still worthwhile to understand T-states?” My first response was to think, “Huh? What the heck is a T-state?”
Doing a little more research, I discovered that, yes, there is something called a T-state, and no, it really isn’t relevant any more, at least for mainline Intel(R) processors.
Let me say this again: T-States are no longer relevant!
Contributors: Seung-Woo Kim, Vardhan Dugar, Jun De Vega