17.10.2014 Views

Xeon-Phi-Coprocessor-Datasheet

Xeon-Phi-Coprocessor-Datasheet

Xeon-Phi-Coprocessor-Datasheet

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.4.2 Thermal Profile and Cooling<br />

The simplest cooling mechanism would involve running fans at full speed. For those<br />

custom air-cooled solutions that intend to be economical in fan power usage and<br />

acoustics, Figure 3-16 represents three regions on the SE10X/7120X coprocessor<br />

power consumption curve relevant to system fan control.<br />

Figure 3-16 SE10X/7120X SKU <strong>Coprocessor</strong> Junction Temperature (T junction) vs Power<br />

105.0<br />

T junction<br />

A 104°C<br />

95.0<br />

Temperature ( o C)<br />

85.0<br />

75.0<br />

C<br />

B<br />

65.0<br />

D<br />

55.0<br />

45.0<br />

0 50 100 150 200<br />

Intel® <strong>Xeon</strong> <strong>Phi</strong> <strong>Coprocessor</strong> Si Power (W)<br />

Region (A-B) on the line represents the minimum necessary performance of a cooling<br />

solution to keep the coprocessor silicon temperature (T junction ) below T throttle of 104°C<br />

(Table 3-2), during high power dissipation. In this region, a cooling solution based on<br />

airflow would ensure the fans are operating at 100% capacity. In region B-C, the<br />

coprocessor power consumption is low enough that the cooling solution may be set to<br />

maintain the junction temperature at a target temperature. Finally, in region C-D, the<br />

coprocessor may need to be cooled to below the target temperature to maintain a<br />

reasonable exhaust air temperature.<br />

Figure Figure 3-17 shows the analogous thermal behavior of T case .<br />

Document ID Number: 328209 003EN<br />

Intel ® <strong>Xeon</strong> <strong>Phi</strong> <strong>Coprocessor</strong> <strong>Datasheet</strong><br />

33

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!