LabVIEW Preventing Other Multi-Core Applications From Running On All Cores Primary Software: LabVIEW Development Systems>>Base PackagePrimary Software Version: 8.5 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: After installing LabVIEW, some applications only execute on a single core. Prior to installation, my applications executed on all cores. This happens regardless of whether or not LabVIEW is open or not. Why is this happening and what can I do to resolve this? Solution: When installing LabVIEW, the installer sets the value of a Windows environment variable, MKL_SERIAL, to YES. This is an Intel Math Kernel Library setting that forces the library to be run in a serial fashion. LabVIEW natively handles multithreading itself and must have MKL_SERIAL set to YES to stream those threads to the library. This allows LabVIEW to intelligently create threads best suited for your specific program. Intel has provided some amount of multi-threading with this library but there are many cases where you need this feature turned off and thus they recommend the application/compiler to handle the multi-threading itself. If your other applications cannot spin their own threads, setting MKL_SERIAL to YES will limit them to execute on a single core environment. This is because those applications rely on the library itself to spin its own threads. If MKL_SERIAL is set to NO and LabVIEW is running, you may experience memory corruption and LabVIEW’s ability to handle threading may be impaired. It is NOT recommended to run LabVIEW under this condition. If you must change the value of this environment variable, ensure that it is set to YES before running LabVIEW. Related Links: Intel® Math Kernel Library 9.0 for Windows Technical User Notes Attachments:
Report Date: 01/29/2008 Last Updated: 02/07/2008 Document ID: 4HSJBBXK |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
