From: Enrico S. <enr...@we...> - 2012-04-19 09:06:02
|
<html style="direction: ltr;"> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"><style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style> </head> <body style="direction: ltr;" bidimailui-detected-decoding-type="UTF-8" bgcolor="#FFFFFF" text="#000000"> I am trying to run several instances of labpython in parallel, to increase performance and balance the load of different threads in my LV application. I still have to dissect and debug the problem, but I suspect that I'm discovering that labpython is not thread safe, in the sense that I get different results depending on the number of workers simultaneously running, and variable results with the same input data from run to run.<br> <br> In this old thread, <a class="moz-txt-link-freetext" href="http://sthmac.magnet.fsu.edu/LV/ILVDigests/2003/12/11/Info-LabVIEW_Digest_2003-12-11_004.html">http://sthmac.magnet.fsu.edu/LV/ILVDigests/2003/12/11/Info-LabVIEW_Digest_2003-12-11_004.html</a> Rolf says:<br> <br> <blockquote type="cite">In LabPython there is some serious locking done as well on the Python<br> system level as the Python system is at this time not safely reentrant<br> but it shouldn't block the LabVIEW UI thread.<br> </blockquote> <br> Possibly related, I also observe frequent occurrences of Error 1047 from PYTHON Set Data when trying to pass variables to a script. These occur mostly when the script is called "too often" or concurrently with other running labpython sessions. The workaround I've found is to feed the script text again to the problematic labpython session (PYTHON Set Script Text) and to recompile (PYTHON Compile Script).<br> <br> Is there still anybody who can shed some light on the details?<br> <br> Enrico<br> <br> </body> </html> |