topic Hi All, in Intel® Integrated Performance Primitives

IPP multithreaded libraries not installed?

dominique120 — Tue, 01 Jul 2014 21:56:49 GMT

Hello

I'm getting this error when I compile my program with Intel's compiler v14:

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Platforms\x64\PlatformToolsets\Intel C++ Compiler XE 14.0\ImportBefore\Intel.Libs.IPP.Intel C++ Compiler XE 14.0.targets(91,5): error : IPP multi-threaded libraries are not installed.

I have Parallel Studio XE 2013 for windows, I thought it came included with IPP, did I miss something?

Thanks

Hi Dominique,

Sergey_K_Intel — Wed, 02 Jul 2014 09:05:14 GMT

Hi Dominique,

You need to reinstall PS2013 in "modify" mode and use "customizing" (or "customize") button on one of installation dialogs. There you need to specify that the installation of IPP multi-threaded libraries is required. By default they are OFF.

Thank you they have been

dominique120 — Wed, 02 Jul 2014 16:16:42 GMT

Thank you they have been installed now. But why does it say (Deprecated)? Has support for them been dropped or is there a problem with using them?

Hi Dominique,

Igor_A_Intel — Mon, 07 Jul 2014 09:08:51 GMT

Hi Dominique,

Multi-threaded libraries are deprecated because internal (inside a primitive) threading is significantly less effective than external (at the application level) threading. Moreover - IPP internally is threaded with OMP, Linux p-threads or Win API or any other threading engine know nothing about OMP and if application is threaded with any other threading tool - you can face with different issues like thread oversubscription, conflicts, etc. With new IPP versions we provide a lot of new APIs for 1D (ipps) and 2D (ippi) functions that support external threading. Several IPP functions combined into 1 pipeline that is threaded externally are significantly more efficient from the performance and power points of view than sequential call of internally-threaded variants of these functions.

regards, Igor

Igor,

Royi — Sat, 30 Apr 2016 13:01:01 GMT

Igor,

I wish you brought back those libraries.
They were the best feature of IPP.

On many cases Multi Threaded Filters are all needed.

Thank You.

So does that mean if I am

acc3141 — Mon, 30 Oct 2017 21:16:05 GMT

So does that mean if I am using the IPP functions in for example a Windows DirectShow Filter where multiple instances may be active within a process then I need to provide my own external locks around calls to IPP functions?.

Hi ,

Chao_Y_Intel — Thu, 09 Nov 2017 07:16:40 GMT

Hi ,
IPP is thread safe libraries. so it could be used by different thread at the same time. It does not need to add a lock externally.

Thanks,
Chao

Hi

Arne_B_ — Mon, 24 Sep 2018 20:35:06 GMT

But if i need just to do a single function on single data continuously, lets say a 2d fourier transform possibly on a big data chunk, and at the same time is unable or dont have the time to do a good optimization myself and yet this function dominates execution time and uses its core up 100%, is it still not a good reason to use the multithreaded version?

ArneBo

Hi All,

Pavel_B_Intel1 — Tue, 25 Sep 2018 06:10:54 GMT

Hi All,

as Igor mentioned IPP team introduced Threading Layer for IPP libraries. It realizes the same functionality as IPP multi-threaded libraries and additionally enable a customer to organize threading for a custom pipeline that has much better performance vs. IPP threaded libraries. The Threading Layer are supported OpenMP and TBB tools starting from IPP 2019 gold release.

In a one of next IPP 2019 updates you can see an example of usage IPP Threading Layer in several modes and you can see performance benefits.

Yes there are a small % of cases when internal threading gives better performance results vs. external threading. But in general external threading is more effective.

Pavel