Unix*

New tool available in beta: Vectorization Advisor

Software must be both threaded and vectorized to get the full performance benefit from today’s and tomorrow’s hardware.  Vectorization Advisor is a vectorization analysis tool that lets you identify loops that will benefit most from vectorization, identify what is blocking effective vectorization, explore the benefit of alternative data reorganizations, and increase the confidence that vectorization is safe.  

Vectorization Advisor is now available for beta test as a part of Intel® Advisor XE 2016. 

The Intel® Parallel Studio XE 2016 Beta program is now available!

Intel Parallel Studio XE 2016 is being made available now as part of a beta test program. In this beta test, you will have early access to Intel® Parallel Studio XE 2016 products and the opportunity to provide feedback to help make our products better. Registration is easy through the pre-Beta survey site

This suite of products brings together exciting new technologies along with improvements to Intel’s existing software development tools:

Troubleshooting HOWTO: Bad hardware? MPSS? Configuration?

Are you having problems with your hardware (Cannot see your Intel(R) Xeon Phi(tm) coprocessor?  Sporadic accessibility?) or with the Intel(R) Manycore Platform Software Stack (Intel(R) MPSS) running reliably?

Attached to this post are PDF "flowcharts" that explain how you can troubleshoot the problem (note:  Both Linux and Windows flowcharts are available), and shows what information you will want to collect if you need to escalate your issue to your OEM provider or Intel.

What collateral/documentation do you want to see?

Do you have questions that you are not finding the answers for in our documentation?  Need more training, source code examples, on what specifically?   Help us understand what's missing so that we can make sure we develop documentation you care about (what is important, and what is nice to have)!   Thank you

FAQS: Compilers, Libraries, Performance, Profiling and Optimization.

In the period prior to the launch of Intel® Xeon Phi™ coprocessor, Intel collected questions from developers who had been involved in pilot testing. This document contains some of the most common questions asked. Additional information and Best-Known-Methods for the Intel Xeon Phi coprocessor can be found here.

The Intel® Compiler reference guides can be found at:

Check if a process is running on the Intel Phi

Hi everyone,

For energy measurement purposes I need to run a program "X" on the Intel phi, that detects when a program "Y" is running in the Intel phi.

Program X runs natively on the Intel Phi (I launch it directly from an ssh terminal logged in the Intel Phi) while program Y is offloaded from the host using micnativeloadex

Here is the code I use in program X, to find if a process is running is a function, that takes in parameter the name of the process:

How to use VTune with ssh public key?

Hello.

My system forces users to use public key to access to not only the host system but also its coprocessors. I just want to collect some performance data from the Xeon Phi. (My application works in native mode.) So I ran the VTune tool with a command like the below.

 

 amplxe-cl -collect knc-lightweight-hotspots -result-dir ./analysis -target-system=mic-native -- ssh -i ~/.ssh/id_rsa_phi root@mic0 "application.out" 

 

But I just got the permission denied errors.

 

Distinguishing OFFLOAD_REPORT statements between multiple nodes

Hello all,

So I have three nodes, each with 2 Xeon Phi (5110P). I'm using OFFLOAD_REPORT to gather all of its wonderful information; however I'm unable to distinguish which Xeon Phi corresponds to a particular node. For each node, each MIC is numbered 0-N, where N is the number of Xeon Phi on that node (in my case, 2). So for a 3 node system, the offload report generates 3 offload reports with identical tags and MIC ID's. See below for some sample output.

订阅 Unix*