Introduction Cygwin* ( http://Cygwin.com/ ) is a popular choice among users seeking a Linux*-like working environment under Windows*. Cygwin* is not an officially supported environment by the Intel® C++ and Intel® Visual Fortran Compilers for Windows* ( http://software.Intel.com/en-us/Intel-compilers/ ); however, setting up the Intel® Compilers for Windows* for use under the Cygwin* bash shell environment is very easy and the compilers are very compatible, functional, and usable.
Read the original post:
A method for using Intel Compilers for Windows* under the Cygwin* bash shell
Abstract Memory sub-system components contribute significantly to the performance characteristics of an application. As an increasing number of threads or processes share the limited resources of cache capacity and memory bandwidth, the scalability of a threaded application can become constrained. Memory-intensive threaded applications can suffer from memory bandwidth saturation as more threads are introduced
Go here to see the original:
Detecting Memory Bandwidth Saturation in Threaded Applications
There are about ~15-20% of IPP functions are threaded internally by OpenMP. A list of the threaded primitives in the IPP library is provided in the ThreadedFunctionsList.txt file located in the library’s doc directory. The quickest way to multi-thread an Intel IPP application is to use the built-in OpenMP threading function directly, which mean when you call any of the threaded funtions on multi-core machine, your program will run in parallel automatically. But some users noticed the cpu usage is ”much” higher than expected. This article list several possible scenarios and provide solution for this. Problem : Scenario 1 : as the comments under the article Deprecated API list since Intel IPP v6.0 I2R D&T Team : I have noticed that when calling the function ippResize or ippResizeCenter recursively and sequentially with small delay (< 100 ms) in between , uses less CPU usage as compared to ippResizeSqrPixel. ......, I have tried using the single algorithm or parallel algorithm introduced in the documentation but it still uses a lot of CPU usage in both algorithms.
Go here to read the rest:
High CPU usage and Intel® IPP threaded function
Abstract Allocating memory from the system heap can be an expensive operation due to a lock used by system runtime libraries to synchronize access to the heap. Contention on this lock can limit the performance benefits from multithreading
More here:
Avoiding Heap Contention Among Threads
This article contains a training material (in PDF format) on Intel® MKL Fast Fourier Transforms (FFT) which includes details of MKL DFTI API, example code and parallelization.
Original post:
Intel® MKL FFT Training Material
Note : this article only applies to Intel® Cluster Ready partners. Background The Intel® Cluster Runtimes 2.1-2 for Linux* is a single source package of runtime components and libraries.
See more here:
Distribution of the Intel® Cluster Runtimes License
Symptom The process_check module of Intel Cluster Checker sometimes reports an issue related to Cluster SSH : Stale Process Check, (process_check)……………………………………………………….FAILED subtest ‘Percent cpu usage is greater than 5%’ failed – failing host compute-00-14 returned: ‘pid=8736 (cssh)’ Resolution Configure Intel® Cluster Checker to ignore the CPU usage of Cluster SSH: cssh
Here is the original post:
Using Cluster SSH with Intel® Cluster Checker
Introduction Intel® AES instructions are a new set of instructions available beginning with the all new 2010 Intel® Core™ processor family based on the 32nm Intel® microarchitecture codename Westmere. These instructions enable fast and secure data encryption and decryption, using the Advanced Encryption Standard (AES) which is defined by FIPS Publication number 197
Read more:
Intel® Advanced Encryption Standard (AES) Instructions Set – Rev 3
Problem : When debugging with Intel’s debugger, idb, if the application encounters an error in the Fortran compiler runtime library, the application exits without returning control to the debugger. This makes it impossible to obtain a stack trace to locate the error or to continue debugging
View original here:
how to get a stack trace in the debugger after an RTL error
Symptom The Intel® Cluster Checker test dat_conf verifies that the file /etc/dat.conf does not contain any entries known to affect some versions of Platform MPI* (formerly HP MPI*). The error may appear similar to the following example: Valid dat.conf entries, (dat_conf)……………………………….FAILED subtest ‘Device: ehca0′ failed – failing hosts compute-00-00 – compute-00-05 returned: ‘/etc/dat.conf contains Interface Adapter entries known to trigger a fault in HP MPI version 2.2.5 or earlier. Please contact Hewlett-Packard for more information.’ Cause Some versions of the Open Fabrics Enterprise Distribution (OFED) insert example entries into /etc/dat.conf. However, some older versions of HP MPI / Platform MPI assume that all /etc/dat.conf entries are valid and active. Resolution Remove or comment out all entries in /etc/dat.conf that are not valid. These lines must be removed/commented out like so: For example, the following two entries have been commented out by inserting the ‘#’ character at the beginning of the line: # OpenIB-mlx4_0-1 u1.2 nonthreadsafe default libdaplscm.so.1 dapl.1.2 “mlx4_0 1″ “” # OpenIB-mlx4_0-2 u1.2 nonthreadsafe default libdaplscm.so.1 dapl.1.2 “mlx4_0 2″ “”
Read the original post:
How to resolve dat_conf issues affecting Platform MPI
