This article discussions parallelization and provides links that will help you understand your programming environment and evaluate the suitability of your app.
This recipe describes how to get, build, and run Quantum ESPRESSO* on the Intel® Xeon Phi™ x200 processor family (previously code-named "Knights Landing" or "KNL"). However, this articles seamlessly applies to any Intel® Xeon® processor, and also summarizes some best known methods for using Intel Software Development Tools with Quantum Espresso (QE) on Intel® architecture-based systems. The...
Intel has a multitude of awesome software development tools, including ones for innovating and optimizing media
Intel® Advisor provides two design tools to help ensure your Fortran, C and C++ native/managed applications realize full performance potential on modern processors, such as Intel® Xeon Phi™ processors. This page augments code-specific advice offered in the vectorization analysis tool with links to web-based vectorization resources.
MILC software represents a set of codes written by the MIMD Lattice Computation collaboration used to study quantum chromodynamics, the theory of the strong interactions of subatomic physics. This article provides instructions for code access, build, and run directions for the “ks_imp_rhmc” application on Intel® Xeon® processors and Intel® Xeon Phi™ processors.
This document demonstrates the best methods to obtain peak memory bandwidth performance on Intel® Xeon Phi™ Processor (codenamed Knights Landing). This is done using STREAM* benchmarks, the de facto industry-standard benchmark for the measurement of computer memory bandwidth.
This article completes an analysis of a problem erroneously reported on the Intel® Developer Zone forum: Vectorization failed because of unsigned integer? It provides a more detailed examination showing that unsigned integer is not impacting compiler vectorization but what methodology to use when a modern C/C++ compiler fails to auto-vectorize for-loops.
Vish Viswanathan, Karthik Kumar, Thomas Willhalm, Patrick Lu, Blazej Filipiak
For more complete information about compiler optimizations, see our Optimization Notice.